Vulnerabilities (CVE)

Filtered by vendor Auth0 Subscribe
Filtered by product Nextjs-auth0
Total 4 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2025-67490 1 Auth0 1 Nextjs-auth0 2026-03-06 N/A 5.4 MEDIUM
The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.
CVE-2025-67716 1 Auth0 1 Nextjs-auth0 2026-03-06 N/A 5.7 MEDIUM
The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. Versions 4.9.0 through 4.12.1 contain an input-validation flaw in the returnTo parameter, which could allow attackers to inject unintended OAuth query parameters into the Auth0 authorization request. Successful exploitation may result in tokens being issued with unintended parameters. This issue is fixed in version 4.13.0.
CVE-2021-43812 1 Auth0 1 Nextjs-auth0 2024-11-21 5.8 MEDIUM 6.4 MEDIUM
The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. Versions before 1.6.2 do not filter out certain returnTo parameter values from the login url, which expose the application to an open redirect vulnerability. Users are advised to upgrade as soon as possible. There are no known workarounds for this issue.
CVE-2021-32702 1 Auth0 1 Nextjs-auth0 2024-11-21 4.3 MEDIUM 8.0 HIGH
The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. Versions before and including `1.4.1` are vulnerable to reflected XSS. An attacker can execute arbitrary code by providing an XSS payload in the `error` query parameter which is then processed by the callback handler as an error message. You are affected by this vulnerability if you are using `@auth0/nextjs-auth0` version `1.4.1` or lower **unless** you are using custom error handling that does not return the error message in an HTML response. Upgrade to version `1.4.1` to resolve. The fix adds basic HTML escaping to the error message and it should not impact your users.