SAML Single Sign On <= 5.0.0 - Unauthenticated Privilege Escalation
Strategic Overview
- Status
- Patched in 6.0.0
- Affected Plugin
- SAML Single Sign On – SSO Login
- Affected Version
<= 5.0.0- CVSS
- 7.3High
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-82842
At a glance
CVE-2026-82842 is a high-severity Improper Privilege Management vulnerability in the SAML Single Sign On WordPress plugin, affecting versions <= 5.0.0. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.0.0; sites on affected versions should update now. Disclosed September 2026, reported by Karthik Ramakrishnan.
Vulnerability Overview
The SAML Single Sign On plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 5.0.0. This is due to insufficient restriction on the capabilities a user may grant themselves. This makes it possible for unauthenticated attackers to elevate their privileges beyond those intended for their role.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-269: Improper Privilege Management
Reaching this weakness in SAML Single Sign On <= 5.0.0 takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For SAML Single Sign On the fix is 6.0.0: builds <= 5.0.0 are affected, anything from 6.0.0 onward is not.
Remediation
Update to version 6.0.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: SAML Single Sign On 6.0.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in SAML Single Sign On – SSO Login
- 9.8CVE-2026-61979: SAML Single Sign On – SSO Login Privilege Escalation
CVE-2026-61979 - 9.8CVE-2026-15981: SAML Single Sign On <= 5.4.4 Authentication Bypass
CVE-2026-15981 - 9.8CVE-2026-15013: SAML Single Sign On <= 5.4.3 Authentication Bypass
CVE-2026-15013 - 8.8SAML Single Sign On – SAML SSO Login <= 4.8.75 CSRF
- 7.5CVE-2026-75807: SAML Single Sign On <= 5.4.6 Authentication Bypass
CVE-2026-75807 - 6.1CVE-2022-4496: SAML Single Sign On Open Redirect
CVE-2022-4496 - 6.1SAML Single Sign On – SAML SSO Login <= 4.9.20 Reflected XSS
- 6.1CVE-2020-6850: SAML Single Sign On – SAML SSO Login <= 4.8.83 XSS
CVE-2020-6850
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C