# CVE-2026-122220: WPO365 LOGIN before 45.2 SAML Replay Protection Bypass


- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-72vv-ff63-gjjc

## What is CVE-2026-122220?

CVE-2026-122220 is a critical vulnerability in WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN), published on 4 Nov 2026. 

### Official description

WPO365 | LOGIN (wpo365-login) plugin before version 45.2 contains an authentication bypass by capture-replay vulnerability caused by a non-functional anti-replay check in Saml2_Service::check_message_id(), which never persists processed SAML message IDs to the wpo365_saml_message_ids transient due to a logic error that returns before saving. Attackers who capture a validly-signed SAMLResponse can replay it to the ACS endpoint repeatedly within its assertion validity window to log in as the victim, including administrators, without detection since the duplicate message ID check never triggers.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2026-122220?


## How do I fix CVE-2026-122220?

No fix has been published for CVE-2026-122220 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-122220 being exploited?

There is no known exploitation of CVE-2026-122220 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-122220 and fix it if it is affected.

What it is: CVE-2026-122220 is a critical vulnerability in WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN), published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-122220 in the wild and no public exploit code.

Affected product: WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-122220/ (Markdown: https://insights.sbomify.com/CVE-2026-122220/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-122220
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-122220
- OSV: https://osv.dev/vulnerability/CVE-2026-122220

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-122220/
Summaries are generated and may contain mistakes; the official description above is the record.