Skip to main content
CVE-2026-107759VulnerabilityPublished

The WPO365 | MICROSOFT 365 GRAPH MAILER plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-107759· High 7.2

Not known to be exploited · CVSS 7.2 High · patch available : patch WPO365 | MICROSOFT 365 GRAPH MAILER (WordPress plugin) soon.

Data as of 31 Oct 2026, 10:38 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.2
Patch
Available
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
wpo365WPO365 | MICROSOFT 365 GRAPH MAILERAffected
  • <=6.2
Fixed in–

AI-suggested

If you cannot patch yet, consider disabling the Graph Mailer feature or completing OAuth authorization immediately after activation to reduce exposure. Avoid using mail-sending features that forward submitter-controlled subjects until the vulnerability is addressed.

Description

The WPO365 | MICROSOFT 365 GRAPH MAILER plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in the 'Subject' parameter used in mail-sending features. This vulnerability affects all versions up to and including 6.2 and allows unauthenticated attackers to inject malicious scripts that execute when a user views the affected page. The issue arises due to insufficient input sanitization and output escaping, particularly when OAuth authorization is not completed immediately after plugin activation.

References

Community reviews

Loading reviews…