Radar sectionsDatabase
Check my site
WordPress plugin

OAuth Single Sign On – SSO (OAuth Client) <= 6.26.12 — Authentication Bypass via get_resource_owner_from_id_token()

CVE-2025-9485Published · Updated

Action summary

Affected: ≤6.26.12Update to 6.26.13 or newer

All remediation steps
Severity
Critical9.8
CVSS
9.8
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High
Weakness
CWE-347 Improper Verification of Cryptographic Signature
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

OAuth Single Sign On – SSO (OAuth Client) miniorange-login-with-eve-online-google-facebook

  1. Affected≤ 6.26.12
  2. Patched in6.26.13

Update to 6.26.13 or newer.

You are affected if you run ≤ 6.26.12. Version 6.26.13 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under OAuth Single Sign On – SSO (OAuth Client).
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 6.26.13, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch OAuth Single Sign On – SSO (OAuth Client) to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Jonas Benjamin Friedli.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in OAuth Single Sign On – SSO (OAuth Client)

All 14
More vulnerabilities in OAuth Single Sign On – SSO (OAuth Client)
SeverityVulnerabilityCVEPublished
Critical9.8Unauthenticated Privilege Escalation
≤7.1.3Update to 7.1.4
CVE-2026-120844
Medium5.3Unauthenticated Authentication Bypass
≤7.1.2Update to 7.1.3
CVE-2026-97274
High7.3Unauthenticated Arbitrary User Account Takeover
≤7.0.0Update to 7.0.1
CVE-2026-82183
Medium5.3Missing Authorization
≤7.0.0Update to 7.0.1
CVE-2026-28008
Medium5.3Missing Authorization
≤6.26.14Update to 6.26.15
CVE-2025-10753

Timeline

  1. CVE published

    Severity critical, CVSS 9.8

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?