# CVE-2025-9485: OAuth Single Sign On – SSO (OAuth Client) <= 6.26.12 - Authentication Bypass via get_resource_owner_from_id_token()

> Unauthenticated attackers can bypass authentication via unsafe JWT processing to access any user account or create subscriber accounts.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-44hx-mv5h-wj6c

## What is CVE-2025-9485?

CVE-2025-9485 is a critical authentication bypass vulnerability in cyberlord92 OAuth Single Sign On – SSO (OAuth Client), published on 4 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress is vulnerable to Improper Verification of Cryptographic Signature in versions up to, and including, 6.26.12. This is due to the plugin performing unsafe JWT token processing without verification or validation in the `get_resource_owner_from_id_token` function. This makes it possible for unauthenticated attackers to bypass authentication and gain access to any existing user account - including administrators in certain configurations - or to create arbitrary subscriber-level accounts.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2025-9485?


## How do I fix CVE-2025-9485?

No fix has been published for CVE-2025-9485 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-9485 being exploited?

There is no known exploitation of CVE-2025-9485 in the wild and no public exploit code.

Public exploit code:

- https://github.com/jFriedli/CVE-2025-9485 (github_poc): https://github.com/jFriedli/CVE-2025-9485

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9485 and fix it if it is affected.

What it is: CVE-2025-9485 is a critical authentication bypass vulnerability in cyberlord92 OAuth Single Sign On – SSO (OAuth Client), published on 4 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9485 in the wild and no public exploit code.

Affected product: cyberlord92 OAuth Single Sign On – SSO (OAuth Client). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-9485/ (Markdown: https://insights.sbomify.com/CVE-2025-9485/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9485
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9485
- OSV: https://osv.dev/vulnerability/CVE-2025-9485

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-9485/
Summaries are generated and may contain mistakes; the official description above is the record.