Approved changes feed: RSS · Atom
cpe:2.3:a:@better-auth:sso:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | @Better Auth (89fe5bf2-a8c5-517f-918c-0e44e54f0594) |
|---|---|
| Product | Sso (cf9a3a45-2b68-5be6-a05b-eb6f000dd801) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-53515 |
vulnerable | 2026-07-29 01:00:27.049185 |
Better Auth: Privilege escalation via SSO provider registration: missing admin role check in @better-auth/sso
HIGH (7.1)
Better Auth is an authentication and authorization library for TypeScript. From 1.2.10 until 1.6.11, the @better-auth/sso plugin's POST /sso/register endpoint lets any organization member attach a new SSO provider to that organization because registerSSOProvider checks only for a membership row and does not require an owner or admin role, allowing attacker-controlled OIDC or SAML providers to drive /sso/callback/{providerId} organization provisioning. This issue is fixed in version 1.6.11.
Published: 2026-07-15T17:27:00.291Z
Updated: 2026-07-15T19:30:08.165Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-53513 |
vulnerable | 2026-07-29 01:00:27.048572 |
Better Auth: Server-side request forgery via unvalidated OIDC endpoints on @better-auth/sso provider registration
CRITICAL (9.6)
Better Auth is an authentication and authorization library for TypeScript. Prior to 1.6.11, the @better-auth/sso plugin's POST /sso/register and POST /sso/update-provider endpoints accept attacker-controlled oidcConfig.userInfoEndpoint, tokenEndpoint, and jwksEndpoint URLs when skipDiscovery: true is set, store them on the ssoProvider row without origin validation, and fetch them during OIDC callback, allowing non-blind server-side request forgery and possible account linking when trustEmailVerified: true is configured. This issue is fixed in version 1.6.11.
Published: 2026-07-15T17:15:59.611Z
Updated: 2026-07-15T19:29:02.266Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.