CVE-2025-48370: auth-js Vulnerable to Insecure Path Routing from Malformed User Input
auth-js is an isomorphic Javascript library for Supabase Auth. Prior to version 2.70.0, the library functions getUserById, deleteUser, updateUserById, listFactors and deleteFactor did not require the user supplied values to be valid UUIDs. This could lead to a URL path traversal, resulting in the wrong API function being called. Implementations that follow security best practice and validate user controlled inputs, such as the userId are not affected by this. This issue has been patched in version 2.70.0.
Security readout for executives and security teams
Plain-English summary
Supabase auth-js before 2.70.0 could misroute certain administrative API requests when an application passed malformed, user-controlled identifiers. This might invoke the wrong API function and affect limited confidentiality or integrity. Applications already validating identifiers as UUIDs are not affected according to the advisory.
Executive priority
Treat this as a routine, low-severity remediation rather than an emergency. Prioritize systems running vulnerable versions where external input reaches administrative authentication functions without UUID validation. Upgrade during the next appropriate maintenance cycle, accelerating remediation for internet-facing or security-sensitive identity workflows.
Technical view
The affected getUserById, deleteUser, updateUserById, listFactors, and deleteFactor functions accepted identifiers without UUID validation. Malformed values could alter URL path routing and cause an unintended API function call. Supabase corrected the issue in auth-js 2.70.0. The supplied CVSS 4.0 score is 2.7.
Likely exposure
Exposure is limited to applications using Supabase auth-js earlier than 2.70.0 that pass unvalidated, user-controlled values into affected functions. Implementations enforcing UUID validation before these calls are described as unaffected. Actual business impact depends on whether these functions are reachable through attacker-influenced application flows.
Exploitation context
The source bundle provides no evidence of active exploitation, and the CVE is not listed as KEV. Its CVSS vector records exploit maturity as unreported. Network reachability and low attack complexity are noted, but practical exploitation depends on an application accepting malformed identifiers and forwarding them to affected functions.
Researcher notes
The issue is categorized under CWE-22 and CWE-287, reflecting path manipulation and authentication-related routing concerns. The source bundle attributes limited confidentiality and integrity impact, with no availability impact. Evidence does not establish which unintended API functions are reachable or the precise authorization consequences, so implementation-specific testing is necessary.
Mitigation direction
Upgrade Supabase auth-js to version 2.70.0 or later.
Validate user and factor identifiers as UUIDs before calling affected functions.
Review vendor guidance and the linked security advisory before deployment.
Restrict attacker influence over inputs passed to administrative authentication functions.
Validation and detection
Inventory deployed auth-js versions and identify installations earlier than 2.70.0.
Trace whether user-controlled values reach any of the five affected functions.
Confirm UUID validation occurs before every affected library call.
After upgrading, verify dependency resolution selects auth-js 2.70.0 or later.
Run regression tests confirming malformed identifiers are rejected without unintended API routing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.