CVE-2026-91830: Subscribe to Comments information disclosure vulnerability
medium 6.5 published 2026-10-16
- Affected versions
- older than 2.3.3
- Fixed in
- 2.3.3
- Latest version
- 2.3.3
- Severity
- Medium · CVSS 6.5
- Active installs
- 10,000+
- Type
- Information disclosure
What an attacker needs
- Access: None. No account or login is needed.
CVSS vector (score by CISA ADP): CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
What to do now
- Update Subscribe to Comments to 2.3.3 or newer: Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- Not sure which version you run? Check your version against every known Subscribe to Comments issue.
With WP-CLI:
wp plugin get subscribe-to-comments --field=version. - If you ran an affected version and something looks off (new admin users, spam pages, redirects), run the free scan below.
The advisory
The Subscribe to Comments WordPress plugin before 2.3.3 does not sign or validate a cookie it trusts to identify a commenter, allowing unauthenticated attackers to disclose a subscriber's management key and silently alter that subscriber's subscriptions.
References
- NVD CVE-2026-91830 nvd.nist.gov
- WPScan advisory wpscan.com
Related
Ran an affected version? Check your site for signs of a hack
The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.
Where this data comes from
- CVE record, score and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Versions and install counts: wordpress.org/plugins/subscribe-to-comments (Plugins API), fetched 2026-11-04.
- The summary, “what an attacker needs” and “what to do” sections are our plain-English reading of the record and the plugin's release history; the quoted description is the record's own text. Spot an error? Email Daniel.