Login By Auth0WordPress extension · Auth0
CVE-2020-6753
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 · uneditedThe Login by Auth0 plugin before 4.0.0 for WordPress allows stored XSS on multiple pages, a different issue than CVE-2020-5392.
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 · moderate confidenceThe Login by Auth0 WordPress plugin before version 4.0.0 contains a stored cross-site scripting (XSS) vulnerability affecting multiple admin pages. Attackers can inject malicious JavaScript through plugin settings or forms that persists in the database and executes when administrators view affected pages.
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
Login By 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 the Login by Auth0 plugin versionAccess your WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Login by Auth0' or 'Auth0', and check the version number displayed under the plugin nameAffected if The displayed version is lower than 4.0.0 or no version number is shown (indicating an unpatched release)
-
Confirm the plugin is activeIn the same Plugins screen, verify that the Auth0 plugin has an 'Active' status or check for a green activation indicatorAffected if The plugin is currently active and the version is below 4.0.0
-
Inspect the plugin settings for injected contentNavigate to the Auth0 plugin settings page (usually under Settings > Auth0 or similar), examine all input fields such as tenant name, domain, client ID, custom labels, or any text inputs, and view the page source to check for unexpected script tags or encoded payloadsAffected if The settings contain visible script tags, onclick handlers, or suspicious encoded characters that did not originate from your configuration
-
Query the database for stored XSS patternsAccess your WordPress database via phpMyAdmin or command line, query the wp_options table (or options table with your prefix) for rows where option_name contains 'auth0' or 'login_auth0', and examine option_value fields for script tags, img onerror attributes, or javascript: URIsAffected if Any option_value field contains HTML script tags, event handlers, or suspicious JavaScript code that was not intentionally stored there
You are affected if the Login by Auth0 plugin is installed, active, and running a version below 4.0.0, regardless of whether visible symptoms are present in the admin interface.
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 Login by Auth0 plugin to version 4.0.0 or later to obtain the patched code. If immediate update is not possible, disable the plugin or restrict administrative access as a temporary workaround.
Fix this in Login By Auth0
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6753 — 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-6753 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