WPO365 authentication bypass in SAML signature validation
- Exploited
- No known exploitation
- Fix
- Fixed in 45.4
- Who is exposed
- Not reported
Summary
The WPO365 | LOGIN plugin for WordPress, before the fixed release, fails to confirm that the validated SAML signature covers the element holding the user's identity. An unauthenticated attacker who can obtain one artifact signed by the configured identity provider can forge a response and log in as any user, including administrators.
Written by a model
Original description
The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) WordPress plugin before 45.4 does not ensure the signature validated on a SAML response covers the element the user identity is read from, allowing unauthenticated attackers to forge a response via signature wrapping and log in as any user, including administrators, when they can supply a single artifact signed by the configured identity provider.
What to do
Upgrade to a fixed version: 45.4.
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-129446 (WPO365 < 45.4 - Unauthenticated Authentication Bypass 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-129446 (entry last updated 2026-11-19):
Affected:
- Unknown WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN): fixed in 45.4
Fixed versions: 45.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129446 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129446 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-129446
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-129446
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-129446"}.Affected versions
- Unknown WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN)fixed in 45.4
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 patch0/5No signal
What would change the score
- Would score about 55 if added to CISA KEV
- Would score about 50 if CISA's SSVC rates exploitation active
- Would score about 22 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-129446 |
| Record | NVD · CVE-2026-129446 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | wpscan.com · vulnerability/b8a29125-d8b5-4a54-be43-fc3aa57a01e3 |
Questions about CVE-2026-129446
Is CVE-2026-129446 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-129446?
WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN): before 45.4.
Source: cve.now feed data
How do I fix CVE-2026-129446?
Upgrade to a fixed version: 45.4.
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.