ezyang/htmlpurifier vulnerabilities

Standards compliant HTML filter written in PHP

Registry
Composer
Latest
4.19.1
License
LGPL-2.1-or-later

4 known advisories

The latest version, 4.19.1, is not affected by any of them. Projects on older versions may be.

Update to the latest version:composer require ezyang/htmlpurifier:^4.19.1

Security advisories for ezyang/htmlpurifier

  • MediumGHSA-6rm6-mjmh-86jq17 May 2022

    HTML Purifier Cross-site Scripting (XSS) vulnerability

    Affected
    <4.1.1
    Fixed in
    4.1.1
  • MediumGHSA-jw86-5cjf-mv7917 May 2022

    HTML Purifier allows remote attackers to obtain sensitive information

    Affected
    <=4.2.0
    Fixed in
    No fix released
  • MediumGHSA-3p68-m5qw-9g9w13 May 2022

    HTML Purifier cross-site scripting (XSS) vulnerability

    Affected
    <4.1.0
    Fixed in
    4.1.0
  • MediumGHSA-6fh7-fwqj-mv491 May 2022

    HTML Purifier Cross-site Scripting vulnerability

    Affected
    <2.0.1
    Fixed in
    2.0.1

Which of your client projects still run an old ezyang/htmlpurifier?

NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Composer packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.