WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 44.1 - Missing Authorization
Strategic Overview
- Status
- Patched in 45.0
- Affected Version
<= 44.1- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-102915
At a glance
CVE-2026-102915 is a medium-severity Missing Authorization vulnerability in the WPO365 WordPress plugin, affecting versions <= 44.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 45.0; sites on affected versions should update now. Disclosed October 2026, reported by Michał Wiencek.
Vulnerability Overview
The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 44.1. This is due to a missing capability check on a function. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform an unauthorized action.
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-862: Missing Authorization
Reaching this weakness in WPO365 <= 44.1 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. 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?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. 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)
- 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
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C