Auth0.js
by Auth0
Source repositories
CVEs (7)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2018-6873 | Cri | 0.64 | 9.8 | 0.02 | Apr 4, 2018 | The Auth0 authentication service before 2017-10-15 allows privilege escalation because the JWT audience is not validated. | ||
| CVE-2018-6874 | Hig | 0.57 | 8.8 | 0.01 | Apr 4, 2018 | CSRF exists in the Auth0 authentication service through 14591 if the Legacy Lock API flag is enabled. | ||
| CVE-2018-7307 | Hig | 0.57 | 8.8 | 0.01 | Mar 6, 2018 | The Auth0 Auth0.js library before 9.3 has CSRF because it mishandles the case where the authorization response lacks the state parameter. | ||
| CVE-2017-17068 | Hig | 0.49 | 7.5 | 0.01 | Dec 6, 2017 | A cross-origin vulnerability has been discovered in the Auth0 auth0.js library affecting versions < 8.12. This vulnerability allows an attacker to acquire authenticated users' tokens and invoke services on a user's behalf if the target site or application uses a popup callback… | ||
| CVE-2026-42280 | Hig | 0.46 | 7.1 | 0.00 | May 27, 2026 | Auth0.js is a client-side JavaScript library for Auth0. From 8.11.0 to 9.32.0, under specific preconditions, the Auth0.js SDK may improperly return user profile information using a valid access token when a specifically crafted invalid ID token is provided. This vulnerability is… | ||
| CVE-2020-5263 | Med | 0.29 | 5.5 | 0.01 | Apr 9, 2020 | auth0.js (NPM package auth0-js) greater than version 8.0.0 and before version 9.12.3 has a vulnerability. In the case of an (authentication) error, the error object returned by the library contains the original request of the user, which may include the plaintext password the… | ||
| CVE-2020-15125 | Hig | 0.00 | 7.7 | 0.02 | Jul 29, 2020 | 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… |
- risk 0.64cvss 9.8epss 0.02
The Auth0 authentication service before 2017-10-15 allows privilege escalation because the JWT audience is not validated.
- risk 0.57cvss 8.8epss 0.01
CSRF exists in the Auth0 authentication service through 14591 if the Legacy Lock API flag is enabled.
- risk 0.57cvss 8.8epss 0.01
The Auth0 Auth0.js library before 9.3 has CSRF because it mishandles the case where the authorization response lacks the state parameter.
- risk 0.49cvss 7.5epss 0.01
A cross-origin vulnerability has been discovered in the Auth0 auth0.js library affecting versions < 8.12. This vulnerability allows an attacker to acquire authenticated users' tokens and invoke services on a user's behalf if the target site or application uses a popup callback…
- risk 0.46cvss 7.1epss 0.00
Auth0.js is a client-side JavaScript library for Auth0. From 8.11.0 to 9.32.0, under specific preconditions, the Auth0.js SDK may improperly return user profile information using a valid access token when a specifically crafted invalid ID token is provided. This vulnerability is…
- risk 0.29cvss 5.5epss 0.01
auth0.js (NPM package auth0-js) greater than version 8.0.0 and before version 9.12.3 has a vulnerability. In the case of an (authentication) error, the error object returned by the library contains the original request of the user, which may include the plaintext password the…
- risk 0.00cvss 7.7epss 0.02
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…