SAML Single Sign On < 6.0.0 - Unauthenticated Privilege Escalation via Account Matching
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Privilege escalation
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-269.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | SAML Single Sign On | 4.8.43 to before 6.0.0 | 6.0.0 | Patch available | CNA |
- SAML Single Sign On VendorUnknown Affected 4.8.43 to before 6.0.0 Fixed in 6.0.0 Patch available CNA
Remediation
- Fix · CNA SAML Single Sign On (Unknown) Fixed in 6.0.0
Timeline
- 2026-10-02 Threatist record created from CVE-2026-82842
- 2026-10-03 Alias added: GHSA-c354-pg28-5955
References
Sources
- CVE-2026-82842 · CVE Program
- CVE-2026-82842 · NVD
- FIRST EPSS
- GHSA-c354-pg28-5955 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences