Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

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 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.

Security Impact Summary

This vulnerability carries a LOW severity rating with a CVSS v3.1 score of 3.5, indicating it can be exploited remotely over the network with relatively low complexity though user interaction is required requiring only low-level privileges . The vulnerability impacts limited integrity, for affected systems. Impacting 1 product from markjaquith organizations running these solutions should prioritize assessment and patching.

Historical Context

Reported in 2023, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.

Published

2023-03-05T21:15:09.693

Last Modified

2026-06-16T22:21:49.447

Status

Modified

Source

[email protected]

Severity

CVSSv3.1: 3.5 (LOW)

CVSSv2 Vector

AV:N/AC:L/Au:S/C:N/I:P/A:N

Access Vector: NETWORK
Access Complexity: LOW
Authentication: SINGLE
Confidentiality Impact: NONE
Integrity Impact: PARTIAL
Availability Impact: NONE

Exploitability Score

8.0

Impact Score

2.9

Weaknesses

Type: Secondary
CWE-79

Affected Vendors & Products

Type	Vendor	Product	Version/Range	Vulnerable?
Application	markjaquith	subscribe_to_comments	< 2.0.8	Yes

References

https://github.com/wp-plugins/subscribe-to-comments/commit/9683bdf462fcac2f32b33be98f0b96497fbd1bb6 Patch, Third Party Advisory ([email protected])
https://github.com/wp-plugins/subscribe-to-comments/releases/tag/2.0.8 Third Party Advisory ([email protected])
https://vuldb.com/?ctiid.222321 Permissions Required ([email protected])
https://vuldb.com/?id.222321 Permissions Required, Third Party Advisory ([email protected])
https://github.com/wp-plugins/subscribe-to-comments/commit/9683bdf462fcac2f32b33be98f0b96497fbd1bb6 Patch, Third Party Advisory (af854a3a-2127-422b-91ae-364da2661108)
https://github.com/wp-plugins/subscribe-to-comments/releases/tag/2.0.8 Third Party Advisory (af854a3a-2127-422b-91ae-364da2661108)
https://vuldb.com/?ctiid.222321 Permissions Required (af854a3a-2127-422b-91ae-364da2661108)
https://vuldb.com/?id.222321 Permissions Required, Third Party Advisory (af854a3a-2127-422b-91ae-364da2661108)

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For markjaquith's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.