Plugins · subscribe-to-comments-reloaded · data as of 2026-11-04
Is Subscribe To Comments Reloaded safe? Known vulnerabilities and latest version
- Status
- Closed 2026-04-28
- Known issues on record
- 4
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate subscribe-to-comments-reloaded && wp plugin delete subscribe-to-comments-reloaded
Check your version
Known vulnerabilities
4 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 4 record(s) do not state which versions are affected.
medium 6.5 CVE-2026-4409 · published 2026-05-05
Information disclosure in Subscribe To Comments Reloaded (240119 and older)
- Affected
- 240119 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Subscribe To Comments Reloaded plugin for WordPress is vulnerable to unauthorized modification of data due to a leaked secret key and usage of a weak hash generation algorithm in all versions up to, and including, 240119. This makes it possible for unauthenticated attackers to extract the global key from any public post page, forge authorization keys and manage comment subscription preferences for arbitrary users
high 7.5 CVE-2024-31249 · published 2024-04-10
Information disclosure in Subscribe To Comments Reloaded (220725 and older)
- Affected
- 220725 and older
- Fixed in
- 240119
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Insertion of Sensitive Information into Log File vulnerability in WPKube Subscribe To Comments Reloaded.This issue affects Subscribe To Comments Reloaded: from n/a through 220725.
medium 5.4 CVE-2022-29414 · published 2022-04-29
Cross-site request forgery (CSRF) in Subscribe To Comments Reloaded (211130 and older)
- Affected
- 211130 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Multiple (13x) Cross-Site Request Forgery (CSRF) vulnerabilities in WPKube's Subscribe To Comments Reloaded plugin <= 211130 on WordPress allows attackers to clean up Log archive, download system info file, plugin system settings, plugin options settings, generate a new key, reset all options, change notifications settings, management page settings, comment form settings, manage subscriptions > mass update settings, manage subscriptions > add a new subscription, update subscription, delete Subscription.
high 8.8 CVE-2014-2274 · published 2018-03-19
Cross-site request forgery (CSRF) in Subscribe To Comments Reloaded (140204 and older)
- Affected
- 140204 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
Cross-site request forgery (CSRF) vulnerability in the Subscribe To Comments Reloaded plugin before 140219 for WordPress allows remote attackers to hijack the authentication of administrators for requests that conduct cross-site scripting (XSS) attacks via a request to the subscribe-to-comments-reloaded/options/index.php page to wp-admin/admin.php.
Recent activity
- 2026-04-28 — closed on wordpress.org (Security Issue).
- 2026-05-05 — Information disclosure disclosed (CVE-2026-4409), fix version not stated.
- 2024-04-10 — Information disclosure disclosed (CVE-2024-31249), fixed in 240119.
- 2022-04-29 — Cross-site request forgery (CSRF) disclosed (CVE-2022-29414), fix version not stated.
Get an email when Subscribe To Comments Reloaded has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Subscribe To Comments Reloaded (subscribe-to-comments-reloaded) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Sensitive data exposure (2) · Cross-site request forgery (CSRF) (2)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/subscribe-to-comments-reloaded (Plugins API), fetched 2026-11-04.
- Vulnerabilities: 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.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/subscribe-to-comments-reloaded"><img src="https://laskyr.com/plugins/subscribe-to-comments-reloaded/badge.svg" alt="Subscribe To Comments Reloaded vulnerability status"></a>