Composer auth0/wordpress has 5 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.
| CVE | Title | Severity | CVSS | Affected | Fixed in |
|---|---|---|---|---|---|
| CVE-2023-6813 | Login by Auth0 plugin for WordPress vulnerable to Reflected Cross-Site Scripting | medium | 6.1 | <4.6.1 | 4.6.1 |
| GHSA-2f4r-34m4-3w8q | Auth0 Wordpress plugin Vulnerable to Brute Force Authentication Tags of CookieStore Sessions | critical | 9.1 | <5.3.0 | 5.3.0 |
| GHSA-vfpx-q664-h93m | Auth0 WordPress Plugin has Insufficient Entropy in Cookie Encryption | high | 8.2 | >=5.0.0-BETA0 and <5.6.0 | 5.6.0 |
| GHSA-vvg7-8rmq-92g7 | Auth0 WordPress has Improper Audience Validation via Auth0-PHP SDK Dependency | medium | 6.8 | >=5.0.0-BETA0 and <5.5.0 | 5.5.0 |
| GHSA-862m-5253-832r | Auth0 Wordpress Plugin vulnerable to Deserialization of Untrusted Data | critical | 0.0 | >=5.0.0-BETA0 and <5.1.0 | 5.1.0 |
Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.
# one-time install pip install phpwarden # then phpwarden deps composer.lock
Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command
Install docs How findings are ranked