The SAML SSO Login WordPress plugin through 1.5.2 does not verify that the SAML assertion whose signature it validates
Source GCVE Database
Not known to be exploited.
Data as of 19 Nov 2026, 10:51 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SAML SSO Login | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict access to the plugin and monitor for updates from the vendor. Avoid using affected versions in production environments if possible.
Description
The SAML SSO Login WordPress plugin versions through 1.5.2 contains a vulnerability where it does not verify that the SAML assertion whose signature it validates matches the assertion used to read the user identity. This flaw allows unauthenticated attackers possessing a validly signed assertion for any identity to authenticate as any existing user, including administrators, via XML signature wrapping.