CVE-2026-19842: SAML Single Sign On (WordPress plugin) · Improper Authentication
Affects SAML Single Sign On (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 5.4.7 soon.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.4.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 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 17 Nov 2026.
What to do
Upgrade SAML Single Sign On (WordPress plugin) to 5.4.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SAML Single Sign On | Affected
| Fixed in
|
AI-suggested
Upgrade the SAML Single Sign On WordPress plugin to version 5.4.7 or later, where this vulnerability is fixed. Until then, administrators should avoid using the one-click certificate promotion control and verify certificates manually if possible. Patch status is confirmed fixed in version 5.4.7.
Description
A vulnerability in the SAML Single Sign On WordPress plugin before version 5.4.7 allows improper authentication due to failure to verify the signature of a SAML response before storing its certificate. This flaw enables an attacker to promote their own certificate to a trusted signing certificate with a single click, potentially allowing them to authenticate as any user, including administrators.