CVE-2026-107759 wpo365 CVE debrief

Who should care

Defenders responsible for WordPress installations with the WPO365 | MICROSOFT 365 GRAPH MAILER plugin should assess exposure and prioritize verification and potential updates. This includes reviewing the plugin's configuration, monitoring for exploitation attempts, and ensuring that the plugin is updated to a fixed version. Additionally, defenders should verify that OAuth authorization is completed to prevent exploitation.

Why it matters

The WPO365 | MICROSOFT 365 GRAPH MAILER plugin for WordPress vulnerability allows unauthenticated attackers to inject arbitrary web scripts, which can execute when a user accesses an injected page. Defenders responsible for WordPress installations with this plugin should assess exposure and prioritize verification and potential updates.

• Unauthenticated attackers can inject arbitrary web scripts
• Injected scripts execute when a user accesses an injected page
• Defenders must verify and update the plugin to a fixed version
• Exposure requires verification from official sources

Technical summary

The WPO365 | MICROSOFT 365 GRAPH MAILER plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Subject (via wp_mail/PHPMailer, e.g. CF7 your-subject)' parameter in all versions up to, and including, 6.2 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.

Defensive priority

Defenders should prioritize verifying and updating the plugin to a fixed version, if available, and monitoring for potential exploitation attempts.

Recommended defensive actions

• Verify the plugin version and update to a fixed version, if available
• Monitor for potential exploitation attempts
• Review and adjust the plugin's configuration to prevent unauthorized access
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance

Evidence notes

The CVE record and NVD vulnerability detail provide information on the vulnerability, but the corpus does not establish versions, exploitation, impact, or remediation beyond plugin activation and OAuth authorization state.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.