WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN)

wpo365-login · plugin

Known security vulnerabilities for WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN). Find out in seconds which version runs on your site with WP Lens.

4 known vulnerabilities

2 exploitable without logging in · latest Jul 23, 2026

Listed on wordpress.org · latest 44.1 · last updated Sep 5, 2026 · 10K+ installs

wordpress.org status checked on Oct 2, 2026

Vulnerabilities

CVE-2026-15212unauthenticated · needs a click≤ 43.2
WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 43.2 - Cross-Site Request Forgery to Privilege Escalation via Plugin Settings Update
High 8.8
CVE-2020-26511unauthenticated
The wpo365-login plugin before v11.7 for WordPress allows use of a symmetric algorithm to decrypt a JWT token.
High 7.5
CVE-2025-67961login required≤ 40.0
WordPress WPO365 plugin <= 40.0 - Server Side Request Forgery (SSRF) vulnerability
Medium 6.4
CVE-2024-4706contributor+≤ 27.2
WordPress + Microsoft Office 365 / Azure AD | LOGIN <= 27.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via pintra Shortcode
Medium 6.4

The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).

← Back to directory