How severe is CVE-2020-15125?

CVE-2020-15125 has a CVSS 3.x base score of 7.7, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2020-15125 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (72nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-15125?

CVE-2020-15125 affects Auth0 Auth0.js. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-15125?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2020-15125 published?

CVE-2020-15125 was published on 2020-07-29 and last updated on 2026-06-17.

CVE-2020-15125

CVE-2020-15125 is a high-severity vulnerability in Auth0 Auth0.js with a CVSS 3.x base score of 7.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-209.

Key facts

Severity: High (CVSS 3.x base score 7.7)
CVSS v2: 4.0
EPSS exploit prediction: 2% (72nd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-209
Affected product: Auth0 Auth0.js
Published: 2020-07-29
Last modified: 2026-06-17

Description

In auth0 (npm package) versions before 2.27.1, a DenyList of specific keys that should be sanitized from the request object contained in the error object is used. The key for Authorization header is not sanitized and in certain cases the Authorization header value can be logged exposing a bearer token. You are affected by this vulnerability if you are using the auth0 npm package, and you are using a Machine to Machine application authorized to use Auth0's management API

Frequently asked questions

What is CVE-2020-15125?: In auth0 (npm package) versions before 2.27.1, a DenyList of specific keys that should be sanitized from the request object contained in the error object is used. The key for Authorization header is not sanitized and in certain cases the Authorization header value can be logged exposing a bearer token. You are affected by this vulnerability if you are using the auth0 npm package, and you are using a Machine to Machine application authorized to use Auth0's management API
How severe is CVE-2020-15125?: CVE-2020-15125 has a CVSS 3.x base score of 7.7, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2020-15125 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (72nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-15125?: CVE-2020-15125 affects Auth0 Auth0.js. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-15125?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-15125 published?: CVE-2020-15125 was published on 2020-07-29 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:auth0:auth0.js:*:*:*:*:*:*:*:*

More vulnerabilities in Auth0 Auth0.js

CVE-2018-6873 — Critical (CVSS 9.8): The Auth0 authentication service before 2017-10-15 allows privilege escalation because the JWT audience is not…
CVE-2018-6874 — High (CVSS 8.8): CSRF exists in the Auth0 authentication service through 14591 if the Legacy Lock API flag is enabled.
CVE-2018-7307 — High (CVSS 8.8): The Auth0 Auth0.js library before 9.3 has CSRF because it mishandles the case where the authorization response lacks…
CVE-2017-17068 — High (CVSS 7.5): A cross-origin vulnerability has been discovered in the Auth0 auth0.js library affecting versions < 8.12. This…
CVE-2026-42280 — High (CVSS 7.1): Auth0.js is a client-side JavaScript library for Auth0. From 8.11.0 to 9.32.0, under specific preconditions, the…
CVE-2020-5263 — Medium (CVSS 5.5): auth0.js (NPM package auth0-js) greater than version 8.0.0 and before version 9.12.3 has a vulnerability. In the case…

All CVEs affecting Auth0 Auth0.js →

Other CWE-209 (Generation of Error Message Containing Sensitive Information) vulnerabilities

CVE-2025-62168 — Critical (CVSS 10.0): Squid is a caching proxy for the Web. In Squid versions prior to 7.2, a failure to redact HTTP authentication…
CVE-2025-68110 — Critical (CVSS 9.9): ChurchCRM is an open-source church management system. Versions prior to 6.5.3 may disclose database information in an…
CVE-2025-46658 — Critical (CVSS 9.8): An issue was discovered in ExonautWeb in 4C Strategies Exonaut 21.6. There are verbose error messages.
CVE-2024-28285 — Critical (CVSS 9.8): A Fault Injection vulnerability in the SymmetricDecrypt function in cryptopp/elgamal.h of Cryptopp Crypto++ 8.9, allows…
CVE-2023-40767 — Critical (CVSS 9.8): User enumeration is found in in PHPJabbers Make an Offer Widget v1.0. This issue occurs during password recovery, where…
CVE-2023-40766 — Critical (CVSS 9.8): User enumeration is found in in PHPJabbers Ticket Support Script v3.2. This issue occurs during password recovery,…

Browse all CWE-209 (Generation of Error Message Containing Sensitive Information) vulnerabilities →