HomeWordPress vulnerabilitiesWPO365
WPO365 vulnerabilities
WPO365 has 4 known vulnerabilities in this database. The most recent published record is dated 6 Oct 2026.
- Known vulnerabilities
- 4
- Active installs
- 10,000+
- Latest version
- 44.1
- Last updated
- 5 Sep 2026
- Most recent
- 6 Oct 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
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 |
|---|---|---|---|---|
| Broken access control CVE-2026-102915 | High 8.5 | Up to 44.1 | No fixed version yet | 1 d ago |
| Cross-site request forgery (CSRF) CVE-2026-15212 | High 8.8 | Up to 43.2 | Fixed in a later version (latest 44.1) | 23 Jul 2026 |
| Cross-site scripting (XSS) CVE-2024-4706 | Medium 6.4 | Up to 27.2 | Fixed in a later version (latest 44.1) | 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-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.