How severe is GHSA-6rm6-mjmh-86jq?

No CVSS score has been assigned to GHSA-6rm6-mjmh-86jq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6rm6-mjmh-86jq?

GHSA-6rm6-mjmh-86jq affects the following packages: ezyang/htmlpurifier (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-6rm6-mjmh-86jq?

Update ezyang/htmlpurifier to 4.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6rm6-mjmh-86jq is resolved across your whole dependency graph.

How do I detect GHSA-6rm6-mjmh-86jq in my Packagist dependencies?

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

How do I mitigate GHSA-6rm6-mjmh-86jq if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-6rm6-mjmh-86jq?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6rm6-mjmh-86jq can be triaged on real exposure rather than presence alone.

Is GHSA-6rm6-mjmh-86jq actively exploited in the wild?

No public exploit code has been indexed for GHSA-6rm6-mjmh-86jq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6rm6-mjmh-86jq?

GHSA-6rm6-mjmh-86jq has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 80th 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-6rm6-mjmh-86jq?

GHSA-6rm6-mjmh-86jq 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-6rm6-mjmh-86jq published, and has it been updated?

GHSA-6rm6-mjmh-86jq was published on May 17, 2022 and was last updated on April 23, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-6rm6-mjmh-86jq — ezyang/htmlpurifier

GHSA-6rm6-mjmh-86jq is a Cross-site Scripting (XSS) vulnerability in ezyang/htmlpurifier. A fix is available for ezyang/htmlpurifier — see the affected versions and patch details below.

HTML Purifier Cross-site Scripting (XSS) vulnerability

Also known asCVE-2010-2479

Published

May 17, 2022

Updated

Apr 23, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐘ezyang/htmlpurifier

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Cross-site scripting (XSS) vulnerability in HTML Purifier before 4.1.1, as used in Mahara and other products, when the browser is Internet Explorer, allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezyang/htmlpurifier`	all versions	4.1.1`composer require ezyang/htmlpurifier:^4.1.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezyang/htmlpurifier, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezyang/htmlpurifier to 4.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6rm6-mjmh-86jq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6rm6-mjmh-86jq can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6rm6-mjmh-86jq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-6rm6-mjmh-86jq in your dependencies?

O3 Security finds GHSA-6rm6-mjmh-86jq across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works