Security readout for executives and security teams
Plain-English summary
Applications using vulnerable better-auth releases may accept attacker-controlled login return addresses. A user who follows a crafted authentication flow could be redirected outside the trusted site, potentially exposing sensitive tokens and enabling account takeover.
Executive priority
Prioritize remediation for internet-facing authentication services because successful abuse could expose tokens and compromise accounts. Accelerate investigation where wildcard origins are configured or callback destinations are user-controlled. No active exploitation is established by the supplied sources.
Technical view
Before version 1.1.20, better-auth trustedOrigins validation can be bypassed for certain absolute URLs and wildcard domains. Malicious callbackURL values may pass origin checks and cause an open redirect. The supplied CVSS 4.0 score is 7.1, with network reachability, low complexity, no privileges, and victim participation required.
Likely exposure
Exposure is most likely where better-auth versions earlier than 1.1.20 process user-influenced callbackURL parameters, particularly with absolute URL or wildcard trusted-origin configurations. The source bundle does not identify specific deployed applications or confirm default configuration exposure.
Exploitation context
The bundle reports potential token theft and account takeover, but provides no evidence of active exploitation. The CVE is not listed as KEV in the supplied data. Exploitation requires victim participation according to the provided CVSS vector.
Researcher notes
Assessment is limited to the supplied bundle. The exact bypass conditions, affected configuration patterns, token types, and telemetry indicators are not fully described here. Validate those details against the vendor advisory before determining exploitability in a specific deployment.
Mitigation direction
- Inventory applications and identify better-auth versions earlier than 1.1.20.
- Upgrade affected installations to version 1.1.20 or later after compatibility testing.
- Check the vendor advisory for configuration-specific guidance if immediate upgrading is impossible.
- Revoke exposed tokens and investigate affected accounts if suspicious redirects are found.
Validation and detection
- Confirm package manifests, lockfiles, and deployed runtimes resolve to version 1.1.20 or later.
- Review trustedOrigins configuration for absolute URLs and wildcard domains.
- In staging, verify untrusted external callback destinations are rejected.
- Inspect authentication logs for unusual external callback destinations or subsequent account activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-601: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookupCVE-2025-71403 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N2.84.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
7.1HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-vp58-j275-797x)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: better-auth before 1.1.20 Open Redirect via trustedOrigins BypassCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
URL Redirection to Untrusted Site ('Open Redirect')
URL Redirection to Untrusted Site ('Open Redirect') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.