VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

ezyang/htmlpurifier: vulnerability history, versions and safety

ezyang/htmlpurifier is a package in the Packagist ecosystem. Vulert records 4 vulnerabilities for it across 4 affected ranges, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M4
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ezyang/htmlpurifier vulnerabilities

Vulert verdict on ezyang/htmlpurifier i

Updated on 23 Oct 2026

Careful: one of the 4 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 4 vulnerabilities on record across 1 year, none in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 1 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 4.1.1 (exclusive) 1
up to 4.1.0 (exclusive) 1
up to 2.0.1 (exclusive) 1
all releases, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for ezyang/htmlpurifier

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2007-3498: HTML Purifier Cross-site Scripting Vulnerability 6.1 medium 2.0.1 01 May 2022
HTML Purifier allows remote attackers to obtain sensitive information 5.3 medium No fix published 17 May 2022
CVE-2010-2479: HTML Purifier Cross-site Scripting (XSS) vulnerability in ezyang/htmlpurifier N/A medium 4.1.1 17 May 2022
CVE-2010-4183: HTML Purifier cross-site scripting (XSS) vulnerability in ezyang/htmlpurifier N/A medium 4.1.0 13 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About ezyang/htmlpurifier

Is ezyang/htmlpurifier safe to use?

Vulert records 4 vulnerabilities for ezyang/htmlpurifier in Packagist: 0 critical, 0 high, 4 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does ezyang/htmlpurifier have?

4 vulnerabilities are recorded for ezyang/htmlpurifier in the Packagist ecosystem: 0 critical, 0 high, 4 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ezyang/htmlpurifier vulnerabilities disclosed?

0 vulnerabilities were recorded for ezyang/htmlpurifier in the last 12 months, and the oldest entry in this database dates to 01 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of ezyang/htmlpurifier are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor ezyang/htmlpurifier for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ezyang/htmlpurifier version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.