How severe is CVE-2019-10062?

CVE-2019-10062 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-10062?

CVE-2019-10062 affects the following packages: aurelia-framework (npm). Ecosystems affected: npm.

How do I fix CVE-2019-10062?

Update aurelia-framework to 1.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10062 is resolved across your whole dependency graph.

How do I detect CVE-2019-10062 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aurelia-framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-10062 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2019-10062 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2019-10062, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-10062?

CVE-2019-10062 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-10062?

CVE-2019-10062 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2019-10062 published, and has it been updated?

CVE-2019-10062 was published on May 13, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

CVE-2019-10062 — aurelia-framework

MEDIUM

CVE-2019-10062 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in aurelia-framework. 1 public exploit reference exists, so weaponization risk is real. A fix is available for aurelia-framework — see the affected versions and patch details below.

Cross-site Scripting in aurelia-framework

Also known asGHSA-m6j2-v3gq-45r5

Published

May 13, 2021

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2019-10062 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

268other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

aurelia-frameworknpm

22Kdownloads / week

Description

The HTMLSanitizer class in html-sanitizer.ts in all released versions of the Aurelia framework 1.x repository is vulnerable to XSS. The sanitizer only attempts to filter SCRIPT elements, which makes it feasible for remote attackers to conduct XSS attacks via (for example) JavaScript code in an attribute of various other elements. An attacker might also exploit a bug in how the SCRIPT string is processed by splitting and nesting them for example.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`aurelia-framework`	all versions	1.4.1`npm install aurelia-framework@1.4.1`

Affected Products

1 product · 1 configurations

Application

aurelia frameworkbluespire

≥ 1.0.0 && ≤ 1.3.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The HTMLSanitizer class in html-sanitizer.ts in all released versions of…

gosecure.netNVDMay 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aurelia-framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aurelia-framework to 1.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10062 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-10062 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

templating-resources

3.1/10

Code-Review1/10

Maintained0/10

Branch-Protection0/10

Assessed Sep 28, 2026

Timeline

Disclosed

May 13, 2021

First exploit

May 24, 2021

Last updated

Jul 8, 2026

Identifiers

CVE-2019-10062

GHSA-m6j2-v3gq-45r5

References

Advisoryaurelia.io Advisorygithub.com Advisorynvd.nist.gov Webgithub.com Webdiscourse.aurelia.io Webgosecure.net Packagegithub.com Evidencegosecure.net

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs with CWE-79 are rated as high or higher (top: high).

CVE-2026-91127CVE-2026-77606CVE-2026-84992CVE-2026-77608CVE-2026-77607GHSA-9rcc-pmj8-ffhrCVE-2026-77616CVE-2025-61682Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026