Unauthenticated stored XSS via unescaped JWT claims
Published Oct 10, 2026 · Updated Oct 10, 2026
Stored XSS in WPO365 | LOGIN 44.1 and earlier allows remote attackers to execute scripts via forged id_token claims in WordPress. The plugin stores malicious HTML from base64url-decoded unique_name or iss claims in the wpo365_errors transient for up to three days and renders it without adequate escaping. Injection requires no authentication; execution occurs when an administrator visits the WPO365 wizard page, exposing that browser session to attacker-controlled scripts.
Summary
What happened
Stored XSS in WPO365 | LOGIN 44.1 and earlier allows remote attackers to execute scripts via forged id_token claims in WordPress. The plugin stores malicious HTML from base64url-decoded unique_name or iss claims in the wpo365_errors transient for up to three days and renders it without adequate escaping. Injection requires no authentication; execution occurs when an administrator visits the WPO365 wizard page, exposing that browser session to attacker-controlled scripts.
The record
- CVE
- CVE-2026-96765
- Published
- Oct 10, 2026
- Updated
- Oct 10, 2026
- Vendor
- WPO365
- Product
- WPO365 | LOGIN
- Classifications
- T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 10, 2026CVE publishedPublication date reported by the CVE source.
- Oct 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=44.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started