Login By Auth0WordPress extension · Auth0
CVE-2019-20173
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 Auth0 wp-auth0 plugin 3.11.x before 3.11.3 for WordPress allows XSS via a wle parameter associated with wp-login.php.
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 confidenceThe Auth0 wp-auth0 plugin for WordPress versions 3.11.x before 3.11.3 contains a reflected cross-site scripting (XSS) vulnerability. The wle parameter on wp-login.php is not properly sanitized, allowing attackers to inject malicious JavaScript that executes in the context of authenticated users' sessions.
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
>= 3.11.0, < 3.11.3CVSS 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 Auth0 plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Auth0 Login By Auth0' or check the plugin files in wp-content/plugins/ for the auth0 directoryAffected if The plugin is not installed or not present in the WordPress environment
-
Check the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find Auth0 Login By Auth0, and note the version number displayed. Alternatively, check the main plugin PHP file for the Version header commentAffected if The version is 3.11.0, 3.11.1, or 3.11.2 (any version >= 3.11.0 but < 3.11.3)
-
Confirm the wp-login.php page is accessibleAccess your WordPress site's wp-login.php page in a browser and verify it loads. This is where the vulnerable wle parameter is processedAffected if wp-login.php is accessible and the site uses the Auth0 plugin for authentication
-
Test for the vulnerable wle parameterSubmit a crafted request to wp-login.php with a test value in the wle parameter (e.g., wp-login.php?wle=test) and inspect the response to see if the value is reflected without proper encodingAffected if The wle parameter value is reflected in the response without HTML encoding or sanitization
The environment is affected if Auth0 Login By Auth0 plugin versions 3.11.0 through 3.11.2 are installed and active, and the wp-login.php page reflects the wle parameter without sanitization.
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 data3.11.3
Upgrade the wp-auth0 plugin to version 3.11.3 or later to obtain the security patch that properly sanitizes the wle parameter.
Fix this in Login By 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-2019-20173 — 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-2019-20173 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