Subscribe To Comments Reloaded vulnerabilities
Plugin slug subscribe-to-comments-reloaded · 5 known vulnerabilities · latest disclosed 2026-05-04 · 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.
2 of 5 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Subscribe To Comments Reloaded
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 6.5 | <= 240119 | No fix yet | CVE-2026-4409 | 2026-05-04 | Advisory |
| Medium 5.3 | <= 220725 | 240119 | CVE-2024-31249 | 2024-04-05 | Advisory |
| High 8.8 | <= 211130 | 220502 | CVE-2022-29414 | 2022-04-29 | Advisory |
| Medium 6.1 | < 150820 | 150820 | none | 2015-08-20 | Advisory |
| High 8.8 | <= 140129 | 140219 | CVE-2014-2274 | 2014-02-18 | Advisory |
Check if a site is affected
Enter a site address to see which version of Subscribe To Comments Reloaded and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Subscribe To Comments Reloaded 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 Reloaded 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.