CVE-2025-67716
BaseFortify
Publication date: 2025-12-11
Last updated on: 2026-03-06
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| auth0 | nextjs-auth0 | From 4.9.0 (inc) to 4.12.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-184 | The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an input-validation flaw in the returnTo parameter of the Auth0 Next.js SDK versions 4.9.0 through 4.12.1. It allows attackers to inject unintended OAuth query parameters into the Auth0 authorization request, potentially causing tokens to be issued with unintended parameters.
How can this vulnerability impact me? :
Exploitation of this vulnerability may result in tokens being issued with unintended parameters, which could lead to unauthorized access or manipulation of authentication tokens, potentially compromising the security of your application.
What immediate steps should I take to mitigate this vulnerability?
Upgrade the Auth0 Next.js SDK to version 4.13.0 or later, as this version contains the fix for the input-validation flaw in the returnTo parameter.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by inspecting the usage of the Auth0 Next.js SDK in your application, specifically checking if the version is between 4.9.0 and 4.12.1, which are vulnerable. On the network level, detection involves monitoring OAuth authorization requests for suspicious or malformed 'returnTo' parameters that are not URL encoded and may contain injected OAuth query parameters. There are no specific commands provided in the resources to detect this vulnerability directly. However, you can audit your package version by running commands like `npm list @auth0/nextjs-auth0` to check the installed SDK version. Additionally, you can capture and analyze OAuth authorization requests using tools like `tcpdump` or `Wireshark` to look for unencoded or suspicious 'returnTo' parameters in URLs. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows attackers to inject unintended OAuth query parameters, potentially leading to tokens being issued with unauthorized or manipulated parameters. This can compromise token integrity and confidentiality, which may affect compliance with standards and regulations like GDPR and HIPAA that require protection of user data and secure authentication mechanisms. Therefore, exploitation of this vulnerability could lead to non-compliance due to compromised data security and privacy controls. Mitigation involves upgrading to version 4.13.0 or later where the issue is fixed. [2]