HomeWordPress vulnerabilitiesWPO365
WPO365 vulnerabilities
WPO365 has 9 known vulnerabilities in this database. The most recent published record is dated 22 Nov 2026.
- Known vulnerabilities
- 9
- Active installs
- 10,000+
- Latest version
- 45.2
- Last updated
- 4 Nov 2026
- Most recent
- 22 Nov 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Authentication bypass CVE-2026-132814 | Not scored | Before 45.0 | Fixed in 45.0 | 16 h ago |
| Authentication bypass CVE-2026-129446 | High 8.1 | Before 45.4 | Fixed in 45.4 | 3 d ago |
| Authentication bypass CVE-2026-122220 | Critical 9.1 | Before 45.2 | Fixed in 45.2 | 4 Nov 2026 |
| Authentication bypass CVE-2026-104759 | High 8.1 | Up to 44.1 | Fixed in a later version (latest 45.2) | 10 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-96765 | High 7.2 | Up to 44.1 | Fixed in a later version (latest 45.2) | 10 Oct 2026 |
| Broken access control CVE-2026-102915 | High 8.5 | Up to 44.1 | Fixed in a later version (latest 45.2) | 6 Oct 2026 |
| Cross-site request forgery (CSRF) CVE-2026-15212 | High 8.8 | Up to 43.2 | Fixed in a later version (latest 45.2) | 23 Jul 2026 |
| Cross-site scripting (XSS) CVE-2024-4706 | Medium 6.4 | Up to 27.2 | Fixed in a later version (latest 45.2) | 23 May 2024 |
| Authentication bypass CVE-2020-26511 | High 7.5 | Before 11.7 | Fixed in 11.7 | 2 Oct 2020 |
Read the published descriptions
- CVE-2026-132814, 22 Nov 2026
- The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) WordPress plugin before 45.0 does not verify that a Microsoft ID token was issued for the site's own application and tenant when multi-tenant sign-in is enabled with an empty list of allowed tenants, allowing unauthenticated attackers to log in as an existing user, including an administrator, with a token Microsoft issued to an application they control. CVE record
- CVE-2026-129446, 19 Nov 2026
- 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. CVE record
- CVE-2026-122220, 4 Nov 2026
- WPO365 | LOGIN (wpo365-login) plugin before version 45.2 contains an authentication bypass by capture-replay vulnerability caused by a non-functional anti-replay check in Saml2_Service::check_message_id(), which never persists processed SAML message IDs to the wpo365_saml_message_ids transient due to a logic error that returns before saving. Attackers who capture a validly-signed SAMLResponse can replay it to the ACS endpoint repeatedly within its assertion validity window to log in as the victim, including administrators, without detection since the duplicate message ID check never triggers. CVE record
- CVE-2026-104759, 10 Oct 2026
- 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. CVE record
- CVE-2026-96765, 10 Oct 2026
- The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id_token' parameter in all versions up to, and including, 44.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is stored in the wpo365_errors transient for up to three days by submitting a crafted unauthenticated request with a forged id_token whose base64url-decoded unique_name or iss claim contains malicious HTML, requiring no prior authentication or user interaction beyond an administrator later visiting the WPO365 wizard page. CVE record
- CVE-2026-102915, 6 Oct 2026
- Subscriber Broken Access Control in WPO365 <= 44.1 versions. CVE record
- CVE-2026-15212, 23 Jul 2026
- The WPO365 | Login plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 43.2. This is due to the Ajax_Service::verify_ajax_request() helper gating its wp_verify_nonce() call behind the boolean option 'enable_nonce_check', which is absent from the default 'wpo365_options' array and therefore evaluates to false via get_global_boolean_var(); as a result, the wp_ajax_wpo365_update_settings handler (Ajax_Service::update_settings) accepts POSTs from cross-origin pages and forwards the attacker-supplied 'settings' payload (base64/JSON) to Options_Service::update_options(), which merges every key/value into wpo365_options without a key allowlist. This makes it possible for unauthenticated attackers to overwrite arbitrary plugin options - including enabling the SCIM REST endpoint (enable_scim), planting an attacker-known scim_secret_token, and setting new_usr_default_role to 'administrator' - via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2024-4706, 23 May 2024
- The WordPress + Microsoft Office 365 / Azure AD | LOGIN plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'pintra' shortcode in all versions up to, and including, 27.2 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2020-26511, 2 Oct 2020
- The wpo365-login plugin before v11.7 for WordPress allows use of a symmetric algorithm to decrypt a JWT token. This leads to authentication bypass. CVE record
What to do if you run WPO365
If you run WPO365, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WPO365 vulnerabilities
Free. We email you when a new vulnerability is published for WPO365, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.