SAML SSO Login authentication bypass to admin via SAML signature wrapping
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The SAML SSO Login plugin for WordPress, through version 1.5.2, does not check that the signed SAML assertion is the same one it reads the user's identity from. An unauthenticated attacker who holds a validly signed assertion for any identity could use XML signature wrapping to log in as any existing user, including an administrator.
Written by a model
Original description
The SAML SSO Login WordPress plugin through 1.5.2 does not verify that the SAML assertion whose signature it validates is the same assertion it reads the user identity from, allowing unauthenticated attackers who hold a validly signed assertion for any identity to authenticate as any existing user, including an administrator, through XML signature wrapping.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-108687 (SAML SSO Login - Single Sign On <= 1.5.2 - Unauthenticated Authentication Bypass to Administrator via SAML Signature Wrapping), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-108687 (entry last updated 2026-11-19):
Affected:
- Unknown SAML SSO Login: through 1.5.2
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-108687 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-108687 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-108687
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-108687
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-108687"}.Affected versions
- Unknown SAML SSO Loginthrough 1.5.2
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch5/5No patch listed yet
What would change the score
- Would score about 60 if added to CISA KEV
- Would score about 55 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-108687 |
| Record | NVD · CVE-2026-108687 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | wpscan.com · vulnerability/158599b8-d368-4272-92d1-9ba1052c8119 |
Questions about CVE-2026-108687
Is CVE-2026-108687 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-108687?
SAML SSO Login: through 1.5.2.
Source: cve.now feed data
Related
- CVE-2026-128851Probono Form Basic < 1.3.3 - Unauthenticated Arbitrary File Upload
- CVE-2026-127021Flamix Bitrix24 and WooCommerce Products Sync < 1.7.0 - Unauthenticated Arbitrary File Upload via CommerceML File Exchange
- CVE-2026-75795Edwiser Bridge 4.3.0 - 4.3.4 - Administrator Account Creation via CSRF
- CVE-2026-123132Otter Blocks < 3.2.10 - Unauthenticated Stored XSS via Comment Links
- CVE-2026-117520Dynific Addons for Elementor < 1.3.1 - Subscriber+ Stored XSS via aep_save_config AJAX Action
- CVE-2026-126040WP Ghost (Hide My WP Ghost) 7.0.00 - 7.0.18 - Two-Factor Authentication Bypass via XML-RPC
No corrections so far. Something wrong on this page? Report an error.