dbcve.org
Login By Auth0WordPress extension · Auth0

CVE-2020-7948

HIGH · 8.8 CVSS v3.1 Published 2020-04-01
Fix available
A fix is available. Upgrade to 4.0.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
An issue was discovered in the Login by Auth0 plugin before 4.0.0 for WordPress. A user can perform an insecure direct object reference.

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 confidence

The Login by Auth0 plugin before version 4.0.0 for WordPress contains an Insecure Direct Object Reference (IDOR) vulnerability. This type of flaw allows attackers to bypass authorization by manipulating references to internal objects (such as database IDs or user identifiers) without proper validation.

MitigationUpdate the Login by Auth0 plugin to version 4.0.0 or later to obtain the patched code that properly implements authorization checks on object references.

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
Affected:< 4.0.0

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Login by Auth0 plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Login by Auth0' or check the /wp-content/plugins/auth0/ directory via file manager or FTP
    Affected if The plugin appears in the installed plugins list or the auth0 directory exists in wp-content/plugins
  2. Identify the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on the plugin name to view the version number in the plugin header, or open the auth0.php file in the plugin directory and check the 'Version' header in the plugin comment block
    Affected if A version number is displayed that is below 4.0.0 (for example, 3.x.x series)
  3. Verify the plugin is active
    Check the status column for the Login by Auth0 plugin in WordPress admin > Plugins > Installed Plugins - look for 'Active' status
    Affected if The plugin shows as Active and the version is below 4.0.0

You are affected if the Login by Auth0 plugin is installed, active, and running a version lower than 4.0.0, as only versions below this threshold contain the IDOR vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 4.0.0 or later
Fixed in 4.0.0
Interim mitigation

Update the Login by Auth0 plugin to version 4.0.0 or later to obtain the patched code that properly implements authorization checks on object references.

Fix this in Login By Auth0 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7948 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-7948 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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