Subscribe to Comments · Security record
Is Subscribe to Comments safe?
One known vulnerability affects the current version (2.3.3), and it has no fix yet.
Checked 2 days ago against the WPVulnerability database, for version 2.3.3.
How it’s looked after
- Last release
- Oct 6, 2026 (1 month ago)
- Releases in the last year
- 2
- Tested up to
- WordPress 7.1.4
- Active installs
- 10K+
10 known vulnerabilities
- 1 high
- 3 medium
- 1 low
- 5 not rated
1 affects the current version. 1 has no fix yet.
Disclosed each year
- 20061
- 20091
- 20152
- 20241
- 20264
Every known vulnerability in Subscribe to Comments
Newest first, with any that affect the current version at the top.
Affects the current version · No fix yet · CVE-2026-66706 · Aug 6, 2026 · Wordfence
Fixed in 2.3.3 · CVE-2026-91830 · Oct 16, 2026 · CVE
Fixed in 2.3.3 · CVE-2026-91831 · Oct 13, 2026 · Wordfence
Fixed in 2.3.3 · CVE-2026-91829 · Oct 11, 2026 · Patchstack
Fixed in 2.3.1 · CVE-2024-8792 · Oct 29, 2024 · Wordfence
Fixed in 2.3 · CVE-2015-10133 · Jul 15, 2015 · Wordfence
Fixed in 2.3 · Jul 14, 2015 · Patchstack
Affects 2.0 and earlier · Nov 16, 2009 · Patchstack
Fixed in 2.0.8 · CVE-2006-10001 · Sep 17, 2006 · Wordfence
Fixed in 2.3 · WPScan
Questions about Subscribe to Comments’s security
Is Subscribe to Comments safe to use?
Yes: 1 known vulnerability affects version 2.3.3, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does Subscribe to Comments have known security vulnerabilities?
Yes: 1 known vulnerability affects version 2.3.3, according to WPVulnerability’s database.
Is Subscribe to Comments still maintained?
Yes. Its last release was 1 month ago. No support threads were opened in the last two months.
Is Subscribe to Comments compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.