Security readout for executives and security teams
Plain-English summary
Better Auth SSO could let a low-privileged user make the server contact attacker-chosen OIDC URLs if discovery was skipped. That can expose internal network data through server-side requests and, in certain trustEmailVerified configurations, may affect account linking. The vendor fixed it in 1.6.11.
Executive priority
Treat as urgent for applications offering SSO provider self-service or delegated administration. The issue can turn authentication infrastructure into an internal request proxy and may affect account identity handling in specific configurations.
Technical view
Before 1.6.11, @better-auth/sso stored userInfoEndpoint, tokenEndpoint, and jwksEndpoint values from register/update-provider requests when skipDiscovery was true, without validating origin. Those endpoints were later fetched during OIDC callback, creating non-blind SSRF. The advisory also notes possible account linking when trustEmailVerified is true.
Likely exposure
Exposure is most likely in TypeScript applications using Better Auth or @better-auth/sso versions 0.1.0 through before 1.6.11, especially where SSO provider registration or updates are reachable by low-privileged users and skipDiscovery is enabled.
Exploitation context
The CVSS vector indicates network access, low privileges, no user interaction, and high confidentiality and integrity impact. KEV is false, and the provided sources do not report active exploitation in the wild.
Researcher notes
Focus review on skipDiscovery provider paths, stored OIDC endpoint origins, and trustEmailVerified behavior. Do not assume all Better Auth deployments are exposed; the risky path depends on SSO plugin usage, version, endpoint reachability, and configuration.
Mitigation direction
- Upgrade Better Auth and @better-auth/sso to version 1.6.11 or later.
- Review vendor advisory and release notes for deployment-specific guidance.
- Restrict SSO provider registration and update access to trusted administrators.
- Review skipDiscovery and trustEmailVerified usage in SSO provider configurations.
- Inspect existing SSO provider records for unexpected or untrusted OIDC endpoint URLs.
Validation and detection
- Inventory applications using better-auth or @better-auth/sso below version 1.6.11.
- Check whether POST /sso/register or /sso/update-provider is exposed to low-privileged users.
- Review SSO provider rows for custom userInfoEndpoint, tokenEndpoint, and jwksEndpoint values.
- Confirm production dependencies resolve to Better Auth version 1.6.11 or later.
- Audit logs for unusual OIDC callback traffic to unexpected internal or external endpoints.
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-20: 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 lookupCWE-345: 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 lookupCWE-441: 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 lookupCWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-53513 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
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A: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
1 official scoreWe 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:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N3.15.8GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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
- https://github.com/better-auth/better-auth/security/advisories/GHSA-5rr4-8452-hf4vCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/better-auth/better-auth/pull/9574CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/better-auth/better-auth/commit/37f60cb176cb53147da7dfd5ec15afa5b486e81eCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/better-auth/better-auth/releases/tag/v1.6.11CVE reference, GitHub_M · x_refsource_MISC
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.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Unintended Proxy or Intermediary ('Confused Deputy')
Unintended Proxy or Intermediary ('Confused Deputy') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.