Summary
CVE-2026-82842 is an unauthenticated privilege escalation vulnerability in the SAML Single Sign On – SSO Login WordPress plugin (miniOrange), affecting all versions before 6.0.0. The plugin fails to honor the site’s configured criterion for linking an incoming SAML SSO identity to a WordPress account, and instead always resolves the identity by login name. This allows an attacker who controls assertions issued by their own Identity Provider to authenticate as any WordPress account, including an administrator, without proving ownership of that account. The issue carries a CVSS v3.1 base score of 8.1 (High).
Technical details
- Root cause: The plugin does not respect the site administrator’s configured account-matching/linking criterion (e.g., email or unique identifier) for resolving an incoming SSO identity to a local WordPress account. It unconditionally matches the incoming identity by login name regardless of the configured setting.
- Trigger conditions: The attacker must control, or be able to influence, the content of SAML assertions produced by an Identity Provider trusted by the vulnerable site (for example, by registering their own IdP or account with the configured IdP), and set the login-name attribute in the assertion to match a target WordPress account.
- Attack vector: Network — exploitation occurs via the SSO login flow; no prior authentication to the WordPress site is required (PR:N, UI:N).
- Impact: Full account takeover, including takeover of administrator accounts, without proving ownership of the target identity — resulting in loss of confidentiality, integrity, and availability of the affected WordPress site.
Affected software
- SAML Single Sign On – SSO Login WordPress Plugin (miniOrange / miniorange-saml-20-single-sign-on) — all versions prior to 6.0.0
Severity
- CVSS v3.1 Base Score: 8.1 (High)
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Update the SAML Single Sign On – SSO Login plugin to version 6.0.0 or later, which enforces the site’s configured account-matching criterion instead of defaulting to login-name matching.
- If immediate patching is not possible:
- Restrict or tightly control which Identity Providers are trusted by the SSO configuration.
- Review the account-linking/matching configuration and, where possible, disable or avoid login-name-based matching until patched.
- Audit recent administrator and privileged account logins for signs of unauthorized SSO-based access.
- Consider temporarily disabling the SAML SSO login flow for sensitive accounts until the plugin is updated.

