Wp Auth0WordPress extension · Auth0
CVE-2020-5392
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA stored cross-site scripting (XSS) vulnerability exists in the Auth0 plugin before 4.0.0 for WordPress via the settings page.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stored cross-site scripting (XSS) vulnerability exists in the Auth0 plugin before version 4.0.0 for WordPress. The vulnerability is located in the plugin's settings page where user-supplied input is not properly sanitized before being stored and rendered, allowing authenticated attackers to inject malicious scripts that execute in the context of other users viewing the affected settings page.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Auth0WordPress extension
< 4.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Auth0 plugin installationAccess WordPress admin dashboard and navigate to Plugins section, or inspect the wp-content/plugins directory, to confirm the Auth0 (wp-auth0) plugin is present on the system.Affected if The Auth0 plugin is not installed.
-
Determine installed Auth0 plugin versionIn WordPress admin, go to Plugins > Installed Plugins > click on the Auth0 plugin details, or read the main plugin file (e.g., wp-auth0.php) to find the version declaration.Affected if The displayed version is below 4.0.0 (for example, 3.x.x series).
-
Confirm plugin is activeIn WordPress admin under Plugins > Installed Plugins, verify that the Auth0 plugin shows as Active.Affected if The Auth0 plugin is active and running.
-
Verify settings page accessibilityNavigate to the Auth0 plugin settings page (typically under Settings > Auth0 in the WordPress admin) while logged in with a standard subscriber-level account to confirm lower-privilege authenticated users can access it.Affected if Users with limited privileges (such as subscribers) can access and modify the Auth0 settings page.
The environment is affected if the Auth0 WordPress plugin is installed, active, and running a version earlier than 4.0.0, with the settings page accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data4.0.0
Update the Auth0 WordPress plugin to version 4.0.0 or later to remediate this stored XSS vulnerability.
Fix this in Wp Auth0
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5392 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-5392 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data