How severe is GHSA-3p68-m5qw-9g9w?

No CVSS score has been assigned to GHSA-3p68-m5qw-9g9w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3p68-m5qw-9g9w?

GHSA-3p68-m5qw-9g9w affects the following packages: ezyang/htmlpurifier (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-3p68-m5qw-9g9w?

Update ezyang/htmlpurifier to 4.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3p68-m5qw-9g9w is resolved across your whole dependency graph.

How do I detect GHSA-3p68-m5qw-9g9w 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-3p68-m5qw-9g9w 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-3p68-m5qw-9g9w?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3p68-m5qw-9g9w can be triaged on real exposure rather than presence alone.

Is GHSA-3p68-m5qw-9g9w actively exploited in the wild?

No public exploit code has been indexed for GHSA-3p68-m5qw-9g9w 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-3p68-m5qw-9g9w?

GHSA-3p68-m5qw-9g9w has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 58th 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-3p68-m5qw-9g9w?

GHSA-3p68-m5qw-9g9w 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-3p68-m5qw-9g9w published, and has it been updated?

GHSA-3p68-m5qw-9g9w was published on May 13, 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.

GHSA-3p68-m5qw-9g9w: ezyang/htmlpurifier

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs58th percentile — riskier than 58% 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

Multiple cross-site scripting (XSS) vulnerabilities in HTML Purifier before 4.1.0, when Internet Explorer is used, allow remote attackers to inject arbitrary web script or HTML via a crafted (1) background-image, (2) background, or (3) font-family Cascading Style Sheets (CSS) property, a different vulnerability than CVE-2010-2479.

Affected Packages

1 total 1 fixed

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

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.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3p68-m5qw-9g9w 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-3p68-m5qw-9g9w can be triaged on real exposure rather than presence alone.

Tailored to GHSA-3p68-m5qw-9g9w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Multiple cross-site scripting (XSS) vulnerabilities in HTML Purifier before 4.1.0, when Internet Explorer is used, allow remote attackers to inject arbitrary web script or HTML via a crafted (1) background-image, (2) background, or (3) font-family Cascading Style Sheets (CSS) property, a different vulnerability than CVE-2010-2479.

O3 Security · Impact-Aware SCA

Is GHSA-3p68-m5qw-9g9w in your dependencies?

O3 Security finds GHSA-3p68-m5qw-9g9w 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

GHSA-3p68-m5qw-9g9w — ezyang/htmlpurifier