CVE-2026-96765 Cross-site scripting in WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN)
Unauthenticated attackers can inject malicious scripts via the id_token parameter, which execute when administrators visit the plugin's wizard page.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-96765?
CVE-2026-96765 is a high-severity cross-site scripting vulnerability in WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN), published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id_token' parameter in all versions up to, and including, 44.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is stored in the wpo365_errors transient for up to three days by submitting a crafted unauthenticated request with a forged id_token whose base64url-decoded unique_name or iss claim contains malicious HTML, requiring no prior authentication or user interaction beyond an administrator later visiting the WPO365 wizard page.
Weakness: CWE-79
Which versions are affected by CVE-2026-96765?
How do I fix CVE-2026-96765?
No fix has been published for CVE-2026-96765 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-96765 being exploited?
There is no known exploitation of CVE-2026-96765 in the wild and no public exploit code.
Sources
Also known as GHSA-87pp-p526-6wm7.