All-in-One Microsoft 365 & Entra ID / Azure AD SSO Login <= 2.2.5 - Authentication Bypass
Strategic Overview
- Status
- Patched in 2.2.6
- Affected Plugin
- All-in-One Microsoft 365 & Entra ID / Azure AD SSO Login
- Affected Version
<= 2.2.5- CVSS
- 9.8Critical
- Weakness type
- CWE-288 · Authentication Bypass Using an Alternate Path or Channel
- CVE
CVE-2026-2628
At a glance
CVE-2026-2628 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the All-in-One Microsoft 365 & Entra ID / Azure AD SSO Login WordPress plugin, affecting versions <= 2.2.5. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.2.6; sites on affected versions should update now. Disclosed March 2026, reported by Nabil Irawan.
Vulnerability Overview
The All-in-One Microsoft 365 & Entra ID / Azure AD SSO Login plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 2.2.5. This makes it possible for unauthenticated attackers to bypass authentication and log in as other users, including administrators.
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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-288: Authentication Bypass Using an Alternate Path or Channel
Reaching this weakness in All-in-One Microsoft 365 & Entra ID / Azure AD SSO Login <= 2.2.5 takes a caller who can reach the endpoint. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.
The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For All-in-One Microsoft 365 & Entra ID / Azure AD SSO Login the fix is 2.2.6: builds <= 2.2.5 are affected, anything from 2.2.6 onward is not.
Remediation
Update to version 2.2.6, 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: All-in-One Microsoft 365 & Entra ID / Azure AD SSO Login 2.2.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in All-in-One Microsoft 365 & Entra ID / Azure AD SSO Login
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C