A vulnerability, which was classified as problematic, was found in Subscribe to Comments Plugin up to 2.0.7 on WordPress. This affects an unknown part of the file subscribe-to-comments.php. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. Upgrading to version 2.0.8 is able to address this issue. The identifier of the patch is 9683bdf462fcac2f32b33be98f0b96497fbd1bb6. It is recommended to upgrade the affected component. The identifier VDB-222321 was assigned to this vulnerability.
CVE-2006-10001
Score 5.4 from GitHub Security Advisory published 2023-03-05. NVD baseline CVSS 3.5; sources differ by 1.9.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.5
- EG Score
- 5.4(medium)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation1% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 46.9%
- KEV
- Not listed
Published
March 5, 2023
Last Modified
November 21, 2024
References (8)
- cna@vuldbhttps://github.com/wp-plugins/subscribe-to-comments/commit/9683bdf462fcac2f32b33be98f0b96497fbd1bb6
- cna@vuldbhttps://github.com/wp-plugins/subscribe-to-comments/releases/tag/2.0.8
- cna@vuldbhttps://vuldb.com/?ctiid.222321
- cna@vuldbhttps://vuldb.com/?id.222321
- af854a3a-2127-422b-91ae-364da2661108https://github.com/wp-plugins/subscribe-to-comments/commit/9683bdf462fcac2f32b33be98f0b96497fbd1bb6
- af854a3a-2127-422b-91ae-364da2661108https://github.com/wp-plugins/subscribe-to-comments/releases/tag/2.0.8
- af854a3a-2127-422b-91ae-364da2661108https://vuldb.com/?ctiid.222321
- af854a3a-2127-422b-91ae-364da2661108https://vuldb.com/?id.222321
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 28× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 00:49 UTCEG score recompute
- 2026-07-23 00:29 UTCEG score recompute
- 2026-07-22 23:53 UTCEG score recompute
- 2026-07-22 21:33 UTCEG score recompute
- 2026-07-20 17:02 UTCEPSS rescore
- 2026-07-18 09:59 UTCEPSS rescore
- 2026-07-16 16:58 UTCEPSS rescore
- 2026-07-15 16:53 UTCEPSS rescore
- 2026-07-15 01:55 UTCEPSS rescore
- 2026-07-13 22:25 UTCEPSS rescore
- 2026-07-13 06:07 UTCEPSS rescore
- 2026-07-13 06:07 UTCEPSS rescore
- 2026-07-11 08:22 UTCEPSS rescore
- 2026-07-09 19:03 UTCEPSS rescore
- 2026-07-08 15:09 UTCEPSS rescore
- 2026-07-06 02:19 UTCEPSS rescore
- 2026-07-06 02:19 UTCEPSS rescore
- 2026-07-04 06:26 UTCEPSS rescore
- 2026-07-02 14:00 UTCEPSS rescore
- 2026-07-01 15:01 UTCEPSS rescore
- 2026-06-29 14:02 UTCEPSS rescore
- 2026-06-29 14:02 UTCEPSS rescore
- 2026-06-27 03:04 UTCEPSS rescore
- 2026-06-25 13:46 UTCEPSS rescore
- 2026-06-24 14:01 UTCEPSS rescore
Show 49 moreShow fewer
- 2026-06-24 14:01 UTCEPSS rescore
- 2026-06-23 21:29 UTCEPSS rescore
- 2026-06-23 21:29 UTCEPSS rescore
- 2026-06-22 14:22 UTCEPSS rescore
- 2026-06-21 01:56 UTCEPSS rescore
- 2026-06-19 19:22 UTCEPSS rescore
- 2026-06-19 19:22 UTCEPSS rescore
- 2026-06-18 17:49 UTCEPSS rescore
- 2026-06-18 17:49 UTCEPSS rescore
- 2026-06-17 17:49 UTCEPSS rescore
- 2026-06-17 17:49 UTCEPSS rescore
- 2026-06-16 17:49 UTCEPSS rescore
- 2026-06-16 17:49 UTCEPSS rescore
- 2026-06-15 17:44 UTCEPSS rescore
- 2026-06-14 23:13 UTCEPSS rescore
- 2026-06-13 22:56 UTCEPSS rescore
- 2026-06-12 23:08 UTCEPSS rescore
- 2026-06-11 13:55 UTCEPSS rescore
- 2026-06-10 22:14 UTCEPSS rescore
- 2026-06-10 13:17 UTCEPSS rescore
- 2026-06-07 15:21 UTCEPSS rescore
- 2026-06-06 13:44 UTCEPSS rescore
- 2026-06-06 13:44 UTCEPSS rescore
- 2026-06-05 22:43 UTCEPSS rescore
- 2026-06-05 06:07 UTCEPSS rescore
- 2026-06-05 06:07 UTCEPSS rescore
- 2026-06-04 13:09 UTCEPSS rescore
- 2026-06-04 13:09 UTCEPSS rescore
- 2026-06-02 20:10 UTCEPSS rescore
- 2026-06-02 20:10 UTCEPSS rescore
- 2026-06-01 13:49 UTCEPSS rescore
- 2026-06-01 13:49 UTCEPSS rescore
- 2026-06-01 13:49 UTCEPSS rescore
- 2026-05-31 22:28 UTCEPSS rescore
- 2026-05-31 00:13 UTCEPSS rescore
- 2026-05-31 00:13 UTCEPSS rescore
- 2026-05-31 00:13 UTCEPSS rescore
- 2026-05-29 13:40 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-27 13:37 UTCEPSS rescore
- 2026-05-27 13:37 UTCEPSS rescore
- 2026-05-26 13:41 UTCEPSS rescore
- 2026-05-26 13:41 UTCEPSS rescore
- 2026-05-26 07:16 UTCEPSS rescore
- 2026-05-26 07:16 UTCEPSS rescore
- 2026-05-25 05:47 UTCEG score recompute
- 2026-05-25 05:47 UTCGHSA enrichment
- 2026-05-24 16:42 UTCEPSS rescore
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2006-10001?
When was CVE-2006-10001 disclosed?
Is CVE-2006-10001 actively exploited?
What is the CVSS score of CVE-2006-10001?
How do I remediate CVE-2006-10001?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2006-10001
Is Your Infrastructure Affected by CVE-2006-10001?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.