WPO365 at a glance
- 9 publicly disclosed vulnerabilities, 4 of them rated High or Critical. The most recent was disclosed on Nov 4, 2026.
- Ranked #1913 by popularity on WordPress.org (10,000+ active installs).
- The latest version is 45.4 (released Nov 14, 2026). The most recent security fix shipped in 45.2.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your WPO365 version
Enter the WPO365 version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “WPO365”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “WPO365”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (45.4). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known WPO365 vulnerabilities
WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 45.1 - Authentication Bypass via SAML Relay
Missing authorization · CVE-2026-122220
Affected versions: ≤ 45.1
Fixed in: 45.2
Severity: Medium 6.3 · Disclosed Nov 4, 2026
WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 44.1 - Unauthenticated Authentication Bypass via OIDC Nonce Replay via id_token Nonce Verification
Missing authorization · CVE-2026-104759
Affected versions: ≤ 44.1
Fixed in: 45.0
Severity: High 8.1 · Disclosed Oct 9, 2026
WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 44.1 - Unauthenticated Stored Cross-Site Scripting via 'id_token' Parameter (iss / unique_name JWT claims)
Cross-site scripting (XSS) · CVE-2026-96765
Affected versions: ≤ 44.1
Fixed in: 45.0
Severity: High 7.2 · Disclosed Oct 9, 2026
WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 44.1 - Missing Authorization
Missing authorization · CVE-2026-102915
Affected versions: ≤ 44.1
Fixed in: 45.0
Severity: Medium 4.3 · Disclosed Oct 5, 2026
WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 43.2 - Cross-Site Request Forgery to Privilege Escalation via Plugin Settings Update
Cross-site request forgery (CSRF) · CVE-2026-15212
Affected versions: ≤ 43.2
Fixed in: 43.3
Severity: High 8.8 · Disclosed Jul 23, 2026
WPO365 <= 40.0 - Authenticated (Subscriber+) Server-Side Request Forgery
Server-side request forgery (SSRF) · CVE-2025-67961
Affected versions: ≤ 40.0
Fixed in: 40.1
Severity: Medium 6.4 · Disclosed Jan 21, 2026
WordPress + Microsoft Office 365 / Azure AD | LOGIN <= 27.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via pintra Shortcode
Cross-site scripting (XSS) · CVE-2024-4706
Affected versions: ≤ 27.2
Fixed in: 28.0
Severity: Medium 6.4 · Disclosed May 22, 2024
WordPress + Microsoft Office 365 / Azure AD | LOGIN <= 15.3 - Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2021-43409
Affected versions: ≤ 15.3
Fixed in: 15.4
Severity: Medium 6.1 · Disclosed Oct 15, 2021
WPO365 | LOGIN <= 11.6 - Authentication Bypass
Missing authorization · CVE-2020-26511
Affected versions: ≤ 11.6
Fixed in: 11.7
Severity: Critical 9.1 · Disclosed Oct 2, 2020
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 45.1 - Authentication Bypass via SAML RelayMissing authorization · CVE-2026-122220 | ≤ 45.1 | 45.2 | Medium 6.3 | Nov 4, 2026 |
| WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 44.1 - Unauthenticated Authentication Bypass via OIDC Nonce Replay via id_token Nonce VerificationMissing authorization · CVE-2026-104759 | ≤ 44.1 | 45.0 | High 8.1 | Oct 9, 2026 |
| WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 44.1 - Unauthenticated Stored Cross-Site Scripting via 'id_token' Parameter (iss / unique_name JWT claims)Cross-site scripting (XSS) · CVE-2026-96765 | ≤ 44.1 | 45.0 | High 7.2 | Oct 9, 2026 |
| WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 44.1 - Missing AuthorizationMissing authorization · CVE-2026-102915 | ≤ 44.1 | 45.0 | Medium 4.3 | Oct 5, 2026 |
| WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 43.2 - Cross-Site Request Forgery to Privilege Escalation via Plugin Settings UpdateCross-site request forgery (CSRF) · CVE-2026-15212 | ≤ 43.2 | 43.3 | High 8.8 | Jul 23, 2026 |
| WPO365 <= 40.0 - Authenticated (Subscriber+) Server-Side Request ForgeryServer-side request forgery (SSRF) · CVE-2025-67961 | ≤ 40.0 | 40.1 | Medium 6.4 | Jan 21, 2026 |
| WordPress + Microsoft Office 365 / Azure AD | LOGIN <= 27.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via pintra ShortcodeCross-site scripting (XSS) · CVE-2024-4706 | ≤ 27.2 | 28.0 | Medium 6.4 | May 22, 2024 |
| WordPress + Microsoft Office 365 / Azure AD | LOGIN <= 15.3 - Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2021-43409 | ≤ 15.3 | 15.4 | Medium 6.1 | Oct 15, 2021 |
| WPO365 | LOGIN <= 11.6 - Authentication BypassMissing authorization · CVE-2020-26511 | ≤ 11.6 | 11.7 | Critical 9.1 | Oct 2, 2020 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 4, 2026.
Most common weaknesses in WPO365
Missing authorization
4 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Cross-site scripting (XSS)
3 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Cross-site request forgery (CSRF)
1 issue
If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.
Frequently asked questions
Is WPO365 safe to use?
WPO365 is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (45.4) and turn on automatic updates.
How do I find which version of WPO365 my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.