WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 44.1 - Unauthenticated Authentication Bypass via OIDC Nonce Replay via id_token Nonce Verification
Strategic Overview
- Status
- Patched in 45.0
- Affected Version
<= 44.1- CVSS
- 8.1High
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-104759
At a glance
CVE-2026-104759 is a high-severity Improper Authentication vulnerability in the WPO365 WordPress plugin, affecting versions <= 44.1. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 45.0; sites on affected versions should update now. Disclosed October 2026, reported by Wordfence PRISM.
Vulnerability Overview
The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) plugin for WordPress is vulnerable to Authentication Bypass via OIDC Nonce Replay in all versions up to, and including, 44.1 This is due to `Id_Token_Service_Deprecated::process_openidconnect_token()` using the incompatible WordPress core `wp_verify_nonce()` function to validate a nonce produced by `Nonce_Service::create_nonce()` — a 64-character hex value that `wp_verify_nonce()` can never successfully verify — causing the nonce check to silently fail without terminating authentication, so execution continues into `authenticate_oidc_user()` with the attacker-supplied `id_token`. This makes it possible for unauthenticated attackers who have obtained a previously-issued, valid `id_token` for a target account to replay that token and authenticate as any WordPress user, including administrators, resulting in full site takeover. This vulnerability is only exploitable when the `use_id_token_parser_v2` plugin option is enabled, as this is the configuration that routes token processing through the deprecated parser containing the broken nonce check.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-287: Improper Authentication
WPO365 <= 44.1 carries this weakness at process_openidconnect_token(), and reaching it takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For WPO365 the fix is 45.0: builds <= 44.1 are affected, anything from 45.0 onward is not.
Remediation
Update to version 45.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WPO365 45.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN)
- 8.8CVE-2026-15212: WPO365 CSRF to Privilege Escalation
CVE-2026-15212 - 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