Vulnerability in OAuth Single Sign On – SSO (WordPress plugin) (CVE-2025-9485)
Summary
Vulnerability in OAuth Single Sign On – SSO (WordPress plugin) (CVE-2025-9485). Successful exploitation can lead to full system takeover. Exploitable via get_resource_owner_from_id_token.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-9485 has been found in OAuth Single Sign On – SSO (WordPress plugin).
Attackers can target a specific entry point like get_resource_owner_from_id_token over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "OAuth Single Sign On – SSO (WordPress plugin) CVE-2025-9485" on the vendor's site.
CVE-2025-9485 (OAuth Single Sign On – SSO (WordPress plugin)) — CWE-347 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: get_resource_owner_from_id_token
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-347) exists in OAuth Single Sign On – SSO (WordPress plugin). Attackers reach the vulnerable code path via get_resource_owner_from_id_token without authentication.
Check the vendor advisory for the affected versions of OAuth Single Sign On – SSO (WordPress plugin). Attack surface: get_resource_owner_from_id_token.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで OAuth Single Sign On – SSO (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。