CVE-2026-82842: SAML Single Sign On < 6.0.0 - Unauthenticated Privilege Escalation via Account Matching
The SAML Single Sign On WordPress plugin before 6.0.0 does not honour the configured criterion for linking an incoming single sign-on identity to a WordPress account, always resolving the identity by login name whatever the site has chosen, which allows an attacker who can have the site's identity provider assert a login name of their choosing to authenticate as any account, including an administrator, without proving ownership of that account.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
WordPress SAML Single Sign On pluginto a version that resolves this vulnerability.Fixed in 6.0.0 - Compensating control
Ensure the SAML IdP assertions cannot be controlled by an attacker; only allow/establish trust with the legitimate site identity provider and prevent untrusted entities from asserting SSO login identities.
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker must be able to cause the site's identity provider to issue a SAML assertion containing a login name they choose. This could allow them to authenticate as any matching WordPress account, including an administrator.
Are sites affected if they configured account matching using something other than the login name?
Yes. Affected versions always resolve the incoming SSO identity by WordPress login name, regardless of the configured account-linking criterion.
What version fixes the issue?
Upgrade the SAML Single Sign On WordPress plugin to version 6.0.0 or later.