WPO365 <= 40.0 - Authenticated (Subscriber+) Server-Side Request Forgery
Strategic Overview
- Status
- Patched in 40.1
- Affected Version
<= 40.0- CVSS
- 6.4Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2025-67961
At a glance
CVE-2025-67961 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the WPO365 WordPress plugin, affecting versions <= 40.0. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 40.1; sites on affected versions should update now. Disclosed January 2026, reported by Phat RiO.
Vulnerability Overview
The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 40.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.
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-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in WPO365 <= 40.0 takes an account at Subscriber level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For WPO365 the fix is 40.1: builds <= 40.0 are affected, anything from 40.1 onward is not.
Remediation
Update to version 40.1, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPO365 40.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- 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 - 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