{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-75807 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-75807 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-75807 is a high-severity authentication bypass vulnerability in cyberlord92 SAML Single Sign On – SSO Login, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-75807 and fix it if it is affected.\n\nWhat it is: CVE-2026-75807 is a high-severity authentication bypass vulnerability in cyberlord92 SAML Single Sign On – SSO Login, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-75807 in the wild and no public exploit code.\n\nAffected product: cyberlord92 SAML Single Sign On – SSO Login. 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-2026-75807/ (Markdown: https://insights.sbomify.com/CVE-2026-75807/index.md)","id":"CVE-2026-75807","markdown":"https://insights.sbomify.com/CVE-2026-75807/index.md","name":"CVE-2026-75807","record":{"aliases":["GHSA-2pfc-9h54-m36f"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress SSO plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass authentication and gain administrator access by poisoning X.509 certificates in the SAML SSO plugin.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"The SAML Single Sign On – SSO Login plugin for WordPress is vulnerable to Authentication Bypass in versions up to, and including, 5.4.6. This is due to the mo_saml_login_validate() ACS handler persisting the X.509 certificate extracted from an incoming SAMLResponse into the mo_saml_required_certificate option before the signature-validation verdict is enforced, because mo_saml_find_certificate() returns false on a fingerprint mismatch rather than halting execution. This makes it possible for unauthenticated attackers to overwrite the plugin's stored IdP signing certificate with an attacker-controlled value, and subsequently forge SAML assertions for any WordPress account — including administrators — to obtain a fully privileged session. Note: The exploit requires the administrator to perform a repair after receiving the test_config_error_wpsamlerr004 error message during the test configuration.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SAML Single Sign On \u003c= 5.4.6 - Unauthenticated Authentication Bypass via X.509 Certificate Poisoning","id":"CVE-2026-75807","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Denial of service in Armoury Crate","id":"CVE-2026-75808"},"packages":[],"prev":{"headline":"Unauthenticated and Undersized DTLS 1.2 AEAD Record Causes DoS","id":"CVE-2026-75806"},"products":["SAML Single Sign On – SSO Login"],"published":"2026-08-29","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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["cyberlord92"]},"summary":"Unauthenticated attackers can bypass authentication and gain administrator access by poisoning X.509 certificates in the SAML SSO plugin.","url":"https://insights.sbomify.com/CVE-2026-75807/"}