Is subscribe-to-comments (WordPress plugin) vulnerable?

WordPress subscribe-to-comments has 3 known advisories in the phpwarden feed. Feed 2026.10.29.2, updated 2026-10-29.

3advisories

0critical

0on CISA KEV

2no fix recorded

CVE	Title	Severity	CVSS	Affected	Fixed in
CVE-2015-10133	The Subscribe to Comments for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 2.1.2 via the Path to header	high	7.2	`<=2.1.2`	–
CVE-2006-10001	A vulnerability, which was classified as problematic, was found in Subscribe to Comments Plugin up to 2.0.7 on WordPress. This affects an un	low	3.5	`<2.0.8`	`2.0.8`
CVE-2024-8792	The Subscribe to Comments plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appro	medium	6.1	`<=2.3`	–

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden wordpress /var/www/html

# or, without Composer
pipx install phpwarden   &&   phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs How findings are ranked

A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.