dbcve.org
Login By Auth0WordPress extension · Auth0

CVE-2020-7947

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-01
Fix available
A fix is available. Upgrade to 4.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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. It has numerous fields that can contain data that is pulled from different sources. One issue with this is that the data isn't sanitized, and no input validation is performed, before the exporting of the user data. This can lead to (at least) CSV injection if a crafted Excel document is uploaded.

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 confidence

The Login by Auth0 WordPress plugin before version 4.0.0 exports user data to CSV without sanitizing input or validating data from multiple source fields. This allows attackers to inject malicious spreadsheet formulas (starting with =, +, -, @, etc.) into user profile fields, which execute when the exported CSV is opened in Excel or another spreadsheet application, potentially leading to remote code execution or data exfiltration.

MitigationUpdate the Login by Auth0 plugin to version 4.0.0 or later which implements proper input sanitization and output encoding for CSV exports. As a temporary workaround, disable user data exports until the patch is applied.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify the Login by Auth0 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Login by Auth0' or check the plugin files in /wp-content/plugins/auth0/
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, click on 'Login by Auth0' in the plugins list to view details, or inspect the main plugin file (e.g., auth0.php) for the 'Version' header comment
    Affected if The version number is less than 4.0.0 or no version is displayed (indicating an old release)
  3. Identify if CSV export functionality is accessible
    Check if the plugin's user export feature is available - typically found in Auth0 plugin settings under Users or Export sections, or look for export-related files in the plugin directory
    Affected if CSV export functionality exists and is accessible to administrators or exported data has been generated
  4. Inspect user profile fields for suspicious content
    In WordPress admin, review user profiles (Users > All Users > select user) for unusual characters at the start of fields like display name, nickname, or other meta fields - look for =, +, -, @, or tab characters preceding text
    Affected if Any user profile fields contain spreadsheet formula characters (=, +, -, @) as leading characters
  5. Review server access logs for CSV export requests
    Check web server logs (Apache/Nginx) for requests to export endpoints, typically paths containing '/export' or '.csv' related to the Auth0 plugin
    Affected if CSV export requests have been made from the affected plugin version

A user is affected if the Login by Auth0 plugin version is below 4.0.0 and CSV export functionality is or was accessible, or if user profile fields contain unsanitized formula injection characters.

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.

dbcve · scoped
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 which implements proper input sanitization and output encoding for CSV exports. As a temporary workaround, disable user data exports until the patch is applied.

Recommended fix Moderate confidence

4.0.0

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Login by Auth0' plugin
  4. Check the current version - if it's below 4.0.0, an update is needed
  5. Click 'Update Now' or navigate to the plugin's WordPress.org page to download version 4.0.0 or later
  6. If automatic updates are disabled, manually upload the updated plugin zip file
  7. After update, verify the plugin version is 4.0.0 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Login By Auth0 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7947 — 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-7947 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