WPO365 account takeover via OIDC audience check bypass
- Exploited
- No known exploitation
- Fix
- Fixed in 45.0
- Who is exposed
- Not reported
Summary
The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) WordPress plugin does not check that Microsoft sign-in tokens were issued for the site's own application when multi-tenant sign-in is enabled with no allowed tenants listed. This lets unauthenticated attackers log in as existing users, including administrators, using a token Microsoft issued to an application the attacker controls.
Written by a model
Original description
The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) WordPress plugin before 45.0 does not verify that a Microsoft ID token was issued for the site's own application and tenant when multi-tenant sign-in is enabled with an empty list of allowed tenants, allowing unauthenticated attackers to log in as an existing user, including an administrator, with a token Microsoft issued to an application they control.
What to do
Upgrade to a fixed version: 45.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132814 (WPO365 < 45.0 - Unauthenticated Account Takeover via OIDC Audience Verification Bypass), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132814 (entry last updated 2026-11-22):
Affected:
- Unknown WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN): fixed in 45.0
Fixed versions: 45.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132814 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132814 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-132814
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132814
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132814"}.Affected versions
- Unknown WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN)fixed in 45.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 55 if added to CISA KEV
- Would score about 50 if CISA's SSVC rates exploitation active
- Would score about 22 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132814 |
| Record | NVD · CVE-2026-132814 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | wpscan.com · vulnerability/f442b280-573d-43a3-a52b-86dc2571a722 |
Questions about CVE-2026-132814
Is CVE-2026-132814 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-132814?
WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN): before 45.0.
Source: cve.now feed data
How do I fix CVE-2026-132814?
Upgrade to a fixed version: 45.0.
Source: cve.now feed data
Related
- CVE-2026-129446WPO365 < 45.4 - Unauthenticated Authentication Bypass via SAML Signature Wrapping
- CVE-2026-94259SMS Alert < 4.0.4 - Admin+ SQLi via 'ID' Parameter
- CVE-2026-14233LifterLMS < 10.0.5 - Subscriber+ Quiz Question Disclosure via query_quiz_questions
- CVE-2026-133362ThinkRank < 2.21.4 - Authenticated Cross-Section Settings Read and Update via 'category' Parameter
- CVE-2026-127024WordForm < 4.1.6 - Unauthenticated Arbitrary File Upload
- CVE-2026-123136Event Tickets Manager for WooCommerce 1.5.4 - 1.6.1 - Unauthenticated Cross-Product Ticket Price Manipulation
No corrections so far. Something wrong on this page? Report an error.