Subscribe to Comments vulnerabilities
Plugin slug subscribe-to-comments · 7 known vulnerabilities · latest disclosed 2026-10-20 · WordPress.org page
1 vulnerability has no fixed version yet. If you use this plugin, consider disabling or replacing it until a fix is released.
1 of 7 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Subscribe to Comments
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 4.3 | 2.3 to 2.3.2 | 2.3.3 | CVE-2026-91831 | 2026-10-20 | Advisory |
| Medium 5.3 | <= 2.3.2 | 2.3.3 | CVE-2026-91830 | 2026-10-13 | Advisory |
| Medium 6.1 | <= 2.3.2 | 2.3.3 | CVE-2026-91829 | 2026-10-09 | Advisory |
| Medium 5.4 | <= 2.3.1 | No fix yet | CVE-2026-66706 | 2026-08-06 | Advisory |
| Medium 6.1 | <= 2.3 | 2.3.1 | CVE-2024-8792 | 2024-10-29 | Advisory |
| High 7.2 | <= 2.1.2 | 2.3 | CVE-2015-10133 | 2015-07-15 | Advisory |
| Medium 6.1 | <= 2.0.7 | 2.0.8 | CVE-2006-10001 | 2006-09-17 | Advisory |
Check if a site is affected
Enter a site address to see which version of Subscribe to Comments and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Subscribe to Comments plugin safe to use?
1 known issue(s) have no fix yet, so check the table above before using it.
How do I check which version of Subscribe to Comments my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.