How severe is GHSA-m6j2-v3gq-45r5?

No CVSS score has been assigned to GHSA-m6j2-v3gq-45r5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m6j2-v3gq-45r5?

GHSA-m6j2-v3gq-45r5 affects the following packages: aurelia-framework (npm). Ecosystems affected: npm.

How do I fix GHSA-m6j2-v3gq-45r5?

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

How do I detect GHSA-m6j2-v3gq-45r5 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 GHSA-m6j2-v3gq-45r5 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 GHSA-m6j2-v3gq-45r5 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-m6j2-v3gq-45r5, 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 GHSA-m6j2-v3gq-45r5?

GHSA-m6j2-v3gq-45r5 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 GHSA-m6j2-v3gq-45r5?

GHSA-m6j2-v3gq-45r5 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 GHSA-m6j2-v3gq-45r5 published, and has it been updated?

GHSA-m6j2-v3gq-45r5 was published on February 10, 2022 and was last updated on November 8, 2023. 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

Cross-site Scripting in aurelia-frameworkGHSA-m6j2-v3gq-45r5

GHSA-m6j2-v3gq-45r5 is a 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.

Also known asCVE-2019-10062

Published

Feb 10, 2022

Updated

Nov 8, 2023

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.

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 GHSA-m6j2-v3gq-45r5 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 GHSA-m6j2-v3gq-45r5 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works