LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2628: All-in-One Microsoft 365 & Entra ID / Azure AD SSO Login <= 2.2.5 - Authentication Bypass

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This WordPress SSO plugin flaw can let an unauthenticated attacker log in as another site user, including an administrator. For affected sites, the business risk is full website takeover, data exposure, content changes, and service disruption. No active exploitation is stated in the provided sources.

Executive priority

Treat as urgent for any WordPress site using this plugin. The vulnerability can bypass login controls and reach administrator access. Prioritize internet-facing, revenue-generating, or data-sensitive sites first.

Technical view

CVE-2026-2628 is an authentication bypass in All-in-One Microsoft 365 & Entra ID / Azure AD SSO Login for WordPress, reported for versions up to and including 2.2.5. It is mapped to CWE-288 with CVSS 3.1 score 9.8, network exploitable, low complexity, no privileges, and no user interaction.

Likely exposure

Exposure is limited to WordPress sites running the login-with-azure / All-in-One Microsoft 365 & Entra ID / Azure AD SSO Login plugin at version 2.2.5 or earlier. Sites using it for administrator SSO are especially sensitive.

Exploitation context

The provided sources describe unauthenticated authentication bypass and administrator login impact. CISA KEV status is false in the bundle, and no cited source confirms active exploitation or public weaponization.

Researcher notes

Evidence is strong for severity and impact, but the bundle does not name a fixed version or detailed root cause. The affected metadata is sparse, so confirm product identity and versioning against Wordfence, WordPress plugin trac, and vendor release notes.

Mitigation direction

  • Identify all WordPress sites using the affected SSO plugin.
  • Check whether the installed version is 2.2.5 or earlier.
  • Review Wordfence and plugin vendor guidance for a fixed release.
  • Update to a fixed version if one is available from trusted channels.
  • If no fix is available, disable the plugin until vendor guidance is clear.
  • Review administrator accounts and recent login activity for anomalies.

Validation and detection

  • Inventory WordPress plugins and confirm presence of login-with-azure.
  • Record the installed plugin version for each site.
  • Compare versions against the vulnerable range: up to and including 2.2.5.
  • Confirm whether SSO login paths remain enabled after mitigation.
  • Review web, WordPress, and authentication logs for unexpected administrator sessions.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-288: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2628 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-2628Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
cyberlord92All-in-One Microsoft 365 & Entra ID / Azure AD SSO Login0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-288 · source CWE mapping

Authentication Bypass Using an Alternate Path or Channel

Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.