Vulnerability Database · Packagist · Package report

auth0/wordpress: vulnerability history, versions and safety

auth0/wordpress is a package in the Packagist ecosystem. Vulert records 6 vulnerabilities for it across 69 releases, from Jul 2024 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded C2 H1 M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 03 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on auth0/wordpress i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 03 Apr 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 6 vulnerabilities on record across 1 year, 2 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 6 over 1 year · 2 in the last year i
  • Latest disclosure 03 Apr 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 0 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

Every version Vulert holds for auth0/wordpress, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
5.5.0 H1 Yes Details →
5.4.0 H1 M1 Yes Details →
5.3.0 H1 M1 Yes Details →
5.2.1 C1 H1 M1 Yes Details →
5.2.0 C1 H1 M1 Yes Details →
5.1.0 C1 H1 M1 Yes Details →
5.0.1 C2 H1 M1 Yes Details →
5.0.0 C2 H1 M1 Yes Details →
5.0.0-BETA1 C2 H1 M1 Yes Details →
5.0.0-BETA0 C2 H1 M1 Yes Details →
4.6.2 C1 Yes Details →
4.6.1 C1 Yes Details →
4.6.0 C1 M2 Yes Details →
4.5.0 C1 M2 Yes Details →
4.4.0 C1 M2 Yes Details →
4.3.1 C1 M2 Yes Details →
4.3.0 C1 M2 Yes Details →
4.2.0 C1 M2 Yes Details →
4.1.1 C1 M2 Yes Details →
4.1.0 C1 M2 Yes Details →
4.0.0 C1 M2 Yes Details →
3.11.3 C1 M2 Yes Details →
3.11.2 C1 M2 Yes Details →
3.11.1 C1 M2 Yes Details →
3.11.0 C1 M2 Yes Details →
3.10.0 C1 M2 Yes Details →
3.9.0 C1 M2 Yes Details →
3.8.1 C1 M2 Yes Details →
3.8.0 C1 M2 Yes Details →
3.7.3 C1 M2 Yes Details →
3.7.1 C1 M2 Yes Details →
3.7.0 C1 M2 Yes Details →
3.6.2 C1 M2 Yes Details →
3.6.1 C1 M2 Yes Details →
3.6.0 C1 M2 Yes Details →
3.5.2 C1 M2 Yes Details →
3.5.1 C1 M2 Yes Details →
3.5.0 C1 M2 Yes Details →
3.4.0 C1 M2 Yes Details →
3.3.2 C1 M2 Yes Details →
3.2.25 C1 M2 Yes Details →
3.2.24 C1 M2 Yes Details →
3.2.23 C1 M2 Yes Details →
3.2.22 C1 M2 Yes Details →
3.2.21 C1 M2 Yes Details →
3.2.19 C1 M2 Yes Details →
3.2.14 C1 M2 Yes Details →
3.2.10 C1 M2 Yes Details →
3.2.9 C1 M2 Yes Details →
3.2.8 C1 M2 Yes Details →
3.2.5 C1 M2 Yes Details →
3.2.0 C1 M2 Yes Details →
3.1.4 C1 M2 Yes Details →
3.1.3 C1 M2 Yes Details →
3.1.2 C1 M2 Yes Details →
3.1.1 C1 M2 Yes Details →
2.2.0 C1 M2 Yes Details →
2.1.11 C1 M2 Yes Details →
2.1.9 C1 M2 Yes Details →
2.1.8 C1 M2 Yes Details →
2.1.7 C1 M2 Yes Details →
2.1.6 C1 M2 Yes Details →
2.1.5 C1 M2 Yes Details →
2.1.4 C1 M2 Yes Details →
2.1.3 C1 M2 Yes Details →
2.1.2 C1 M2 Yes Details →
2.1.1 C1 M2 Yes Details →
2.1.0 C1 M2 Yes Details →
2.0.0 C1 M2 Yes Details →

Newest 69 of 69 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2
  • 2025 3
  • 2026 1

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

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 auth0/wordpress

Is auth0/wordpress safe to use?

Vulert records 6 vulnerabilities for auth0/wordpress in Packagist: 2 critical, 1 high, 3 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does auth0/wordpress have?

6 vulnerabilities are recorded for auth0/wordpress in the Packagist ecosystem: 2 critical, 1 high, 3 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 auth0/wordpress vulnerabilities disclosed?

2 vulnerabilities were recorded for auth0/wordpress in the last 12 months, and the oldest entry in this database dates to 10 Jul 2024. 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 auth0/wordpress 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 auth0/wordpress for upcoming vulnerabilities?

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