Quick answers
- Is CVE-2026-96765 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96765 being exploited in the wild.
- How severe is CVE-2026-96765?
- High severity, with a CVSS score of 7.2, published 10 October 2026.
- Which products and versions are affected?
- WPO365 | Login up to and including 44.1.
- Is there a fix for CVE-2026-96765?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-96765 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-96765?
- Check whether you run WPO365 | Login at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Stored XSS vulnerability in the id_token parameter allows unauthenticated attackers to inject arbitrary HTML/JavaScript via the unique_name or iss claims of a forged JWT token. The unsanitized payload is stored in the wpo365_errors transient for up to three days and executed when an administrator accesses the WPO365 wizard page, requiring no prior authentication but relying on victim interaction.
Affected products
- WPO365 LOGIN up to and including 44.1
Timeline
- 2026-10-10: disclosed