Is damienharper/auditor-bundle 5.2 vulnerable?

Composer · 7 releases from 5.2.0 to 5.2.6 · latest damienharper/auditor-bundle is 7.2.1 · checked 18 Nov 2026

No known advisories in the last release

damienharper/auditor-bundle 5.2.6, the last 5.2 release, has no known advisories. 1 advisory affects earlier 5.2.x releases, so update to 5.2.6.

Update within 5.2:composer require damienharper/auditor-bundle:^5.2.6

Is your project on an affected damienharper/auditor-bundle?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 5.2.x, affecting earlier releases

  • MediumCVE-2024-45592GHSA-78vg-7v27-hj6710 Sept 2024

    auditor-bundle vulnerable to Cross-site Scripting because name of entity does not get escaped

    Affected
    <5.2.6
    Fixed in
    5.2.6

Every damienharper/auditor-bundle 5.2.x release

Affected: 5.2.0 to 5.2.5. 5.2.6 is not affected. Latest damienharper/auditor-bundle: 7.2.1.

VersionKnown advisories
damienharper/auditor-bundle 5.2.6None
damienharper/auditor-bundle 5.2.5CVE-2024-45592
damienharper/auditor-bundle 5.2.4CVE-2024-45592
damienharper/auditor-bundle 5.2.3CVE-2024-45592
damienharper/auditor-bundle 5.2.2CVE-2024-45592
damienharper/auditor-bundle 5.2.1CVE-2024-45592
damienharper/auditor-bundle 5.2.0CVE-2024-45592

Which of your client projects are still on damienharper/auditor-bundle 5.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact damienharper/auditor-bundle version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other damienharper/auditor-bundle versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.