WordPress plugin
Subscribe To Comments Reloaded security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High2
- Medium3
- Low0
All Subscribe To Comments Reloaded vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High8.8 | Cross-Site Request Forgery ≤211130Update to 220502 | CVE-2022-29414 | |
| High8.8 | Cross-Site Request Forgery to Cross-Site Scripting ≤140129Update to 140219 | CVE-2014-2274 |
- High8.8Cross-Site Request Forgery
≤211130Update to 220502
- High8.8Cross-Site Request Forgery to Cross-Site Scripting
≤140129Update to 140219
Subscribe To Comments Reloaded: common questions
Does Subscribe To Comments Reloaded have known vulnerabilities?
Yes. VulnCrest Radar lists 5 known vulnerabilities in Subscribe To Comments Reloaded: 2 high, 3 medium. At least one is not fixed in the latest version.
How do I check which version of Subscribe To Comments Reloaded I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Subscribe To Comments Reloaded vulnerability?
CVE-2026-4409, published May 4, 2026: Subscribe To Comments Reloaded <= 240119 - Improper Authorization to Unauthenticated Arbitrary Subscription Management. Severity: Medium (CVSS 6.5).
Is any Subscribe To Comments Reloaded vulnerability listed in CISA KEV?
No. None of the known Subscribe To Comments Reloaded vulnerabilities is currently listed in the CISA KEV catalog.