WordPress plugin · subscribe-to-comments-reloaded
Is Subscribe To Comments Reloaded safe?
Closed. Replace it.
wordpress.org closed it on Apr 28, 2026 (security issue), so it gets no more security fixes, and 4 flaws are on record. If your site runs it, move to a maintained alternative.
- Flaws on record
- 4
- High or critical
- 1
- Exploited
- none
Every recorded flaw
- May 4, 2026Subscribe To Comments Reloaded: Unauthorized modification of dataCVE-2026-4409 · affects up to 240119 · reported by WordfenceMedium 6.5
- Apr 10, 2024Subscribe To Comments Reloaded: Insertion of Sensitive Information into Log FileCVE-2024-31249 · affects up to 220725 · reported by PatchstackMedium 5.3
- Apr 29, 2022Multiple (13x) Cross-Site Request Forgery (CSRF) vulnerabilities in WPKube's Subscribe To Comments Reloaded plugin <= 211130 on WordPress allows attackers to clCVE-2022-29414 · affects up to 211130 · reported by PatchstackMedium 5.4
- Mar 19, 2018Cross-site request forgery (CSRF) vulnerability in the Subscribe To Comments Reloaded plugin before 140219 for WordPress allows remote attackers to hijack the aCVE-2014-2274 · fixed in 140219 · reported by MITREHigh 8.8
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.