CVE-2026-2628
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe All-in-One Microsoft 365 & Entra ID SSO Login plugin for WordPress contains an authentication bypass vulnerability in versions up to 2.2.5. The flaw allows unauthenticated attackers to bypass the authentication mechanism and impersonate any user on the WordPress site, including administrators, by manipulating the SSO authentication flow.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate the All-in-One Microsoft 365 & Entra ID SSO Login plugin. Note the version number displayed.Affected if The installed version is 2.2.5 or earlier (versions prior to 2.2.6 contain the vulnerability)
-
Confirm SSO authentication is enabledAccess the plugin settings page in WordPress admin and verify whether the Microsoft 365/Entra ID SSO feature is currently active and configured for user logins.Affected if SSO authentication is enabled and the plugin version falls within the affected range
-
Audit administrative user accountsIn WordPress admin, navigate to Users > All Users and review the list of accounts with Administrator role. Look for unfamiliar accounts, unexpected additions, or accounts created around the time the vulnerability was potentially active.Affected if Unexpected administrator accounts exist or recent privilege escalations are found
-
Examine authentication activity logsCheck WordPress security logs, server access logs, or any SSO audit logs for unusual login activity such as logins occurring at odd hours, from unexpected IP addresses, or multiple failed attempts followed by a successful admin login.Affected if Suspicious authentication patterns are observed that may indicate exploitation attempts
Your environment is affected if the plugin version is 2.2.5 or earlier and SSO authentication is enabled, regardless of whether you observe signs of exploitation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the plugin to version 2.2.6 or later immediately. If immediate update is not possible, disable the plugin and review user accounts for unauthorized administrative access. After patching, verify that the SSO authentication flow functions correctly and monitor for suspicious login activity.
Version 2.2.6 or later (latest available version)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the 'All-in-One Microsoft 365 & Entra ID / Azure AD SSO Login' plugin
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. If no update is shown, manually download the latest version from the WordPress plugin repository at plugins.trac.wordpress.org and upload it via Plugins > Add New > Upload Plugin
- 6. After updating, verify the plugin is active and functioning correctly
- 7. Test the SSO functionality to ensure authentication is working properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2628 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2628 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data