LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71401: better-auth before 1.4.2 basePath Modification DoS

better-auth (npm) before 1.4.2 allows an external request to configure baseURL when it is not otherwise defined (e.g., BETTER_AUTH_URL is unset). An attacker able to make the very first request to the server after startup can poison the router's base path, causing all routes to return 404 for all users (denial of service). The issue is not reachable when baseURL is explicitly configured or on typical managed hosting platforms.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A remote attacker who reaches a vulnerable better-auth server first after startup may corrupt its routing configuration. The service can then return 404 errors across all routes, disrupting authentication and dependent applications until recovery. Exposure requires baseURL to be undefined; explicitly configured deployments and typical managed hosting platforms are reported as not reachable.

Executive priority

Treat exposed, self-hosted deployments as an urgent availability risk because one unauthenticated request at startup can disrupt all routes. Upgrade and confirm explicit configuration promptly. Lower priority only after validating that baseURL is fixed or the deployment model makes the flaw unreachable.

Technical view

In better-auth versions before 1.4.2, an external first request can influence baseURL when no value is configured, poisoning the router’s base path and causing service-wide 404 responses. The supplied CVSS v4.0 score is 9.3. The described outcome is denial of service, contingent on startup timing and missing baseURL configuration.

Likely exposure

Prioritize self-hosted better-auth deployments below 1.4.2 where baseURL or BETTER_AUTH_URL is unset and an external request can arrive immediately after startup. Explicit baseURL configuration prevents the documented path. The bundle also says typical managed hosting platforms are not reachable, but does not identify specific platforms.

Exploitation context

The attack is remote, unauthenticated, and requires the attacker’s request to be the first after server startup. The bundle reports no KEV listing and provides no evidence of active exploitation. Successful abuse causes routing failure and denial of service rather than a documented data breach.

Researcher notes

The supplied sources disagree in labeling: the CVE bundle and GitHub advisory identify versions before 1.4.2, while the VulnCheck reference title says before 1.4.1. Use the vendor advisory and installed-package evidence as authoritative. No active exploitation is established. CWE-770 is assigned, although the described mechanism is router configuration poisoning.

Mitigation direction

  • Upgrade better-auth to version 1.4.2 or later.
  • Explicitly configure baseURL or BETTER_AUTH_URL using the deployment’s trusted canonical URL.
  • Check the vendor advisory for deployment-specific recovery or mitigation guidance.
  • Control external traffic during restarts until configuration and upgrade status are verified.

Validation and detection

  • Inventory better-auth versions and identify every deployment below 1.4.2.
  • Confirm baseURL or BETTER_AUTH_URL is explicitly set before accepting requests.
  • Verify expected routes return normal responses after each restart.
  • Review monitoring for widespread 404 responses beginning immediately after server startup.
  • Confirm managed-hosting assumptions against the vendor advisory and actual deployment configuration.
Prepared
Confidence
medium
Sources
4

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 · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-71401 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NVulnCheck
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H2.23.6VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2025-71401Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
better-authbetter-auth0, 1.4.2unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.