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)?

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-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 60th 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.

🐘 Packagist

Not in CISA KEV

HTML Purifier cross-site scripting (XSS) vulnerabilityGHSA-3p68-m5qw-9g9w

GHSA-3p68-m5qw-9g9w 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.

Also known asCVE-2010-4183

Published

May 13, 2022

Updated

Apr 23, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk

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

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`

Affected Products

1 product · 75 configurations

Application

htmlpurifierhtmlpurifier

≤ 4.0.0

28 versions

1.0.01.0.11.1.01.1.11.1.21.2.01.3.01.3.11.3.21.4.01.4.11.5.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
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.