Auth0
Products
33- 9 CVEs
- 8 CVEs
- 5 CVEs
- 4 CVEs
- 4 CVEs
- 4 CVEs
- 4 CVEs
- 4 CVEs
- 4 CVEs
- 3 CVEs
- 2 CVEs
- 2 CVEs
- 2 CVEs
- 1 CVE
- 1 CVE
- 1 CVE
- 1 CVE
- 1 CVE
- 1 CVE
- 1 CVE
- 1 CVE
- 1 CVE
- 1 CVE
- 1 CVE
- express-jwt1 CVEnpm
- 1 CVE
- 1 CVE
- 1 CVE
- 1 CVE
- 1 CVE
- View all 33 products →
Recent CVEs
63| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2020-7947 | Cri | 0.64 | 9.8 | 0.03 | Apr 1, 2020 | 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… | ||
| CVE-2019-7644 | Cri | 0.64 | 9.8 | 0.02 | Apr 11, 2019 | Auth0 Auth0-WCF-Service-JWT before 1.0.4 leaks the expected JWT signature in an error message when it cannot successfully validate the JWT signature. If this error message is presented to an attacker, they can forge an arbitrary JWT token that will be accepted by the vulnerable… | ||
| 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-2026-85982 | Cri | 0.59 | 9.0 | 0.00 | Sep 8, 2026 | The Auth0 AD/LDAP Connector is vulnerable to stored Cross-Site Scripting (XSS) issues due to improper HTML encoding of data in search results and updater log content displayed in the admin panel. An authenticated user with privileges to modify directory attributes, or a… | ||
| CVE-2020-7948 | Hig | 0.57 | 8.8 | 0.02 | Apr 1, 2020 | 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. | ||
| CVE-2018-15121 | Hig | 0.57 | 8.8 | 0.00 | Aug 29, 2018 | An issue was discovered in Auth0 auth0-aspnet and auth0-aspnet-owin. Affected packages do not use or validate the state parameter of the OAuth 2.0 and OpenID Connect protocols. This leaves applications vulnerable to CSRF attacks during authentication and authorization operations. | ||
| CVE-2015-9235 | Cri | 0.57 | 9.8 | 0.08 | May 29, 2018 | In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family). | ||
| 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-2026-130236 | Hig | 0.55 | 8.5 | 0.00 | Nov 19, 2026 | In the Auth0 Authorization Extension, request authentication handling can process claims from query parameters independently of header validation. Under specific preconditions, this may allow an authenticated tenant user to issue requests to the extension's administrative… | ||
| CVE-2025-48951 | Cri | 0.54 | — | 0.01 | Jun 3, 2025 | Auth0-PHP is a PHP SDK for Auth0 Authentication and Management APIs. Versions 8.0.0-BETA3 prior to 8.3.1 contain a vulnerability due to insecure deserialization of cookie data. If exploited, since SDKs process cookie content without prior authentication, a threat actor could… | ||
| CVE-2025-46572 | Cri | 0.53 | — | 0.00 | May 6, 2025 | passport-wsfed-saml2 provides passport strategy for both WS-fed and SAML2 protocol. A vulnerability present starting in version 3.0.5 up to and including version 4.6.3 allows an attacker to impersonate any user during SAML authentication by crafting a SAMLResponse. This can be… | ||
| CVE-2020-15259 | Hig | 0.53 | 8.1 | 0.01 | Nov 6, 2020 | ad-ldap-connector's admin panel before version 5.0.13 does not provide csrf protection, which when exploited may result in remote code execution or confidential data loss. CSRF exploits may occur if the user visits a malicious page containing CSRF payload on the same machine… | ||
| CVE-2025-47275 | Cri | 0.52 | 9.1 | 0.01 | May 15, 2025 | Auth0-PHP provides the PHP SDK for Auth0 Authentication and Management APIs. Starting in version 8.0.0-BETA1 and prior to version 8.14.0, session cookies of applications using the Auth0-PHP SDK configured with CookieStore have authentication tags that can be brute forced, which… | ||
| CVE-2026-85983 | Hig | 0.51 | 7.8 | 0.00 | Sep 8, 2026 | The Auth0 AD/LDAP Connector improperly processes a configuration value during service startup. This allows a low-privileged user on the host system to modify the connector's configuration. When the service restarts, the modified configuration can lead to code execution with the… | ||
| CVE-2020-15125 | Hig | 0.50 | 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… | ||
| CVE-2020-5391 | Hig | 0.50 | 8.8 | 0.01 | Apr 1, 2020 | Cross-site request forgery (CSRF) vulnerabilities exist in the Auth0 plugin before 4.0.0 for WordPress via the domain field. | ||
| CVE-2018-6874 | Hig | 0.50 | 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-2026-126129 | Hig | 0.49 | 7.5 | 0.00 | Nov 10, 2026 | The Auth0 ASP.NET Core Authentication SDK incorrectly determines a session's OIDC Back-Channel Logout status, which may result in a logged-out session being accepted for access to protected endpoints. | ||
| CVE-2026-126128 | Hig | 0.49 | 7.5 | 0.00 | Nov 10, 2026 | The Management API client in the Auth0 Node.js SDK improperly neutralizes path parameters, allowing a request and its attached management API token to be redirected to an unintended endpoint on the same tenant, resulting in unintended access to data or operations that the… | ||
| CVE-2026-108167 | Hig | 0.49 | 7.5 | 0.00 | Nov 10, 2026 | The auth0-ai-python FGA retriever does not distinguish between authorization checks under different users, relations, or conditions when filtering documents during retrieval-augmented generation, resulting in documents denied by Auth0 FGA being included in the model context and… |
- risk 0.64cvss 9.8epss 0.03
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…
- risk 0.64cvss 9.8epss 0.02
Auth0 Auth0-WCF-Service-JWT before 1.0.4 leaks the expected JWT signature in an error message when it cannot successfully validate the JWT signature. If this error message is presented to an attacker, they can forge an arbitrary JWT token that will be accepted by the vulnerable…
- 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.59cvss 9.0epss 0.00
The Auth0 AD/LDAP Connector is vulnerable to stored Cross-Site Scripting (XSS) issues due to improper HTML encoding of data in search results and updater log content displayed in the admin panel. An authenticated user with privileges to modify directory attributes, or a…
- risk 0.57cvss 8.8epss 0.02
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.
- risk 0.57cvss 8.8epss 0.00
An issue was discovered in Auth0 auth0-aspnet and auth0-aspnet-owin. Affected packages do not use or validate the state parameter of the OAuth 2.0 and OpenID Connect protocols. This leaves applications vulnerable to CSRF attacks during authentication and authorization operations.
- risk 0.57cvss 9.8epss 0.08
In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family).
- 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.55cvss 8.5epss 0.00
In the Auth0 Authorization Extension, request authentication handling can process claims from query parameters independently of header validation. Under specific preconditions, this may allow an authenticated tenant user to issue requests to the extension's administrative…
- risk 0.54cvss —epss 0.01
Auth0-PHP is a PHP SDK for Auth0 Authentication and Management APIs. Versions 8.0.0-BETA3 prior to 8.3.1 contain a vulnerability due to insecure deserialization of cookie data. If exploited, since SDKs process cookie content without prior authentication, a threat actor could…
- risk 0.53cvss —epss 0.00
passport-wsfed-saml2 provides passport strategy for both WS-fed and SAML2 protocol. A vulnerability present starting in version 3.0.5 up to and including version 4.6.3 allows an attacker to impersonate any user during SAML authentication by crafting a SAMLResponse. This can be…
- risk 0.53cvss 8.1epss 0.01
ad-ldap-connector's admin panel before version 5.0.13 does not provide csrf protection, which when exploited may result in remote code execution or confidential data loss. CSRF exploits may occur if the user visits a malicious page containing CSRF payload on the same machine…
- risk 0.52cvss 9.1epss 0.01
Auth0-PHP provides the PHP SDK for Auth0 Authentication and Management APIs. Starting in version 8.0.0-BETA1 and prior to version 8.14.0, session cookies of applications using the Auth0-PHP SDK configured with CookieStore have authentication tags that can be brute forced, which…
- risk 0.51cvss 7.8epss 0.00
The Auth0 AD/LDAP Connector improperly processes a configuration value during service startup. This allows a low-privileged user on the host system to modify the connector's configuration. When the service restarts, the modified configuration can lead to code execution with the…
- risk 0.50cvss 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…
- risk 0.50cvss 8.8epss 0.01
Cross-site request forgery (CSRF) vulnerabilities exist in the Auth0 plugin before 4.0.0 for WordPress via the domain field.
- risk 0.50cvss 8.8epss 0.01
CSRF exists in the Auth0 authentication service through 14591 if the Legacy Lock API flag is enabled.
- risk 0.49cvss 7.5epss 0.00
The Auth0 ASP.NET Core Authentication SDK incorrectly determines a session's OIDC Back-Channel Logout status, which may result in a logged-out session being accepted for access to protected endpoints.
- risk 0.49cvss 7.5epss 0.00
The Management API client in the Auth0 Node.js SDK improperly neutralizes path parameters, allowing a request and its attached management API token to be redirected to an unintended endpoint on the same tenant, resulting in unintended access to data or operations that the…
- risk 0.49cvss 7.5epss 0.00
The auth0-ai-python FGA retriever does not distinguish between authorization checks under different users, relations, or conditions when filtering documents during retrieval-augmented generation, resulting in documents denied by Auth0 FGA being included in the model context and…