CVE-2026-96765
Received Received - Intake

BaseFortify

Publication date: 2026-10-10

Last updated on: 2026-10-10

Assigner: Wordfence

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-10
Last Modified
2026-10-10
Generated
2026-10-10
AI Q&A
2026-10-10
EPSS Evaluated
N/A
NVD
CVE-2026-96765
EUVD
EUVD-2026-96281

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
wpo365 WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a Stored Cross-Site Scripting (XSS) flaw in the WPO365 plugin for WordPress. It allows unauthenticated attackers to inject malicious scripts via the 'id_token' parameter due to insufficient input sanitization. The injected scripts execute when users visit affected pages, and the payload persists in the wpo365_errors transient for up to three days.

Detection Guidance

This vulnerability can be detected by checking for malicious scripts in the wpo365_errors transient or inspecting the id_token parameter for unauthenticated requests. Review WordPress logs for unusual activity and check the WPO365 plugin settings for unauthorized changes.

Impact Analysis

Unauthenticated attackers could steal user sessions, deface websites, or perform actions on behalf of users. Administrators visiting the WPO365 wizard page may trigger the execution of injected scripts, leading to potential data breaches or unauthorized access.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's data protection requirements or HIPAA's safeguards for protected health information. Organizations may face compliance penalties if user data is compromised due to this flaw.

Mitigation Strategies

Immediately update the WPO365 plugin to the latest version. Remove any suspicious scripts from the wpo365_errors transient. Monitor for unauthorized access or changes in the plugin configuration.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-96765. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart