What is CVE-2019-10062?

CVE-2019-10062 is a medium-severity cross-site scripting (XSS) vulnerability in aurelia-framework (npm), affecting versions < 1.4.1. It is fixed in 1.4.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

Which versions of aurelia-framework are affected by CVE-2019-10062?

aurelia-framework (npm) versions < 1.4.1 is affected.

Is there a fix for CVE-2019-10062?

Yes. CVE-2019-10062 is fixed in 1.4.1. Upgrade to this version or later.

Is CVE-2019-10062 exploitable, and should I be worried?

Whether CVE-2019-10062 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2019-10062 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2019-10062 in aurelia-framework

Q: Which versions of aurelia-framework are affected by CVE-2019-10062?

aurelia-framework (npm) versions < 1.4.1 is affected.

Q: Is there a fix for CVE-2019-10062?

Yes. CVE-2019-10062 is fixed in 1.4.1. Upgrade to this version or later.

Q: Is CVE-2019-10062 exploitable, and should I be worried?

Whether CVE-2019-10062 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2019-10062 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2019-10062?

Upgrade aurelia-framework to 1.4.1 or later.

Summary

Cross-site Scripting in aurelia-framework

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.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Affected versions

aurelia-framework (< 1.4.1)

Security releases

aurelia-framework → 1.4.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade aurelia-framework to 1.4.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2019-10062? CVE-2019-10062 is a medium-severity cross-site scripting (XSS) vulnerability in aurelia-framework (npm), affecting versions < 1.4.1. It is fixed in 1.4.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
Which versions of aurelia-framework are affected by CVE-2019-10062? aurelia-framework (npm) versions < 1.4.1 is affected.
Is there a fix for CVE-2019-10062? Yes. CVE-2019-10062 is fixed in 1.4.1. Upgrade to this version or later.
Is CVE-2019-10062 exploitable, and should I be worried? Whether CVE-2019-10062 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2019-10062 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2019-10062? Upgrade aurelia-framework to 1.4.1 or later.