WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 45.1 - Authentication Bypass via SAML Relay
Strategic Overview
- Status
- Patched in 45.2
- Affected Version
<= 45.1- CVSS
- 6.3Medium
- Weakness type
- CWE-294 · Authentication Bypass by Capture-replay
- CVE
CVE-2026-122220
At a glance
CVE-2026-122220 is a medium-severity Authentication Bypass by Capture-replay vulnerability in the WPO365 WordPress plugin, affecting versions <= 45.1. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). The issue is fixed in version 45.2; sites on affected versions should update now. Disclosed November 2026, reported by buiih.
Vulnerability Overview
The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 45.1. This is due to a logic error in Saml2_Service::check_message_id() that returned before persisting processed SAML message IDs to the wpo365_saml_message_ids transient, rendering the anti-replay check non-functional. This makes it possible for unauthenticated attackers to replay a captured, validly-signed SAMLResponse to the ACS endpoint and authenticate as any victim user, including administrators, within the assertion's validity window. SAML 2.0 single sign-on must be enabled and the attacker must be able to capture a legitimately-signed SAMLResponse for the target user.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-294: Authentication Bypass by Capture-replay
A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).
Remediation
Update to version 45.2, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: WPO365 45.2 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN)
- 9.1CVE-2020-26511: WPO365 | LOGIN <= 11.6 Authentication Bypass
CVE-2020-26511 - 8.8CVE-2026-15212: WPO365 CSRF to Privilege Escalation
CVE-2026-15212 - 8.1CVE-2026-104759: WPO365 Authentication Bypass
CVE-2026-104759 - 7.2CVE-2026-96765: WPO365 Stored XSS
CVE-2026-96765 - 6.4CVE-2025-67961: WPO365 <= 40.0 Server-Side Request Forgery
CVE-2025-67961 - 6.4CVE-2024-4706: WordPress + Microsoft Office 365 /… Stored XSS
CVE-2024-4706 - 6.1CVE-2021-43409: WordPress + Microsoft Office 365 /… Stored XSS
CVE-2021-43409 - 4.3CVE-2026-102915: WPO365 Missing Authorization
CVE-2026-102915
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C