CVE-2026-66706: Subscribe to Comments (WordPress plugin) · Cross-site Scripting
Affects Subscribe to Comments (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 5.9 Medium.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 6 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mark JaquithSubscribe to Comments | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, users should consider restricting high privilege access and be cautious with user interactions involving the Subscribe to Comments plugin. Monitor vendor channels for updates.
Description
CVE-2026-66706 is a medium severity cross-site scripting (XSS) vulnerability in the Subscribe to Comments plugin by Mark Jaquith. It affects versions up to and including 2.3.1. The vulnerability involves improper neutralization of input during web page generation, which can lead to reflected or stored XSS attacks. The CVSS score is 5.9, indicating a moderate impact on confidentiality, integrity, and availability. No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.