{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-9485 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-9485 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-9485 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2025-9485 in the wild and no public exploit code.\n\nAffected 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.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-9485/ (Markdown: https://insights.sbomify.com/CVE-2025-9485/index.md)","id":"CVE-2025-9485","markdown":"https://insights.sbomify.com/CVE-2025-9485/index.md","name":"CVE-2025-9485","record":{"aliases":["GHSA-44hx-mv5h-wj6c"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass authentication via unsafe JWT processing to access any user account or create subscriber accounts.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-03-23","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-03-23T14:59:43Z","kind":"github_poc","ref":"https://github.com/jFriedli/CVE-2025-9485","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"OAuth Single Sign On – SSO (OAuth Client) \u003c= 6.26.12 - Authentication Bypass via get_resource_owner_from_id_token()","id":"CVE-2025-9485","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Incorrect Privilege Assignment in GitLab","id":"CVE-2025-9486"},"packages":[],"prev":{"headline":"Missing Authorization in GitLab","id":"CVE-2025-9484"},"products":["OAuth Single Sign On – SSO (OAuth Client)"],"published":"2025-10-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["cyberlord92"]},"summary":"Unauthenticated attackers can bypass authentication via unsafe JWT processing to access any user account or create subscriber accounts.","url":"https://insights.sbomify.com/CVE-2025-9485/"}