CVE-2006-10001
Markjaquith Subscribe To Comments vulnerability
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.
Affected products
Subscribe To Comments. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Markjaquith Subscribe To Comments runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/wp-plugins/subscribe-to-comments/commit/9683bdf462fcac2f32b33be98f0b96497fbd1bb · Patch
- github.com/wp-plugins/subscribe-to-comments/releases/tag/2.0.8 · Third Party Advisory
- vuldb.com/?id.222321 · Third Party Advisory
- vuldb.com/?ctiid.222321
- nvd.nist.gov/vuln/detail/CVE-2006-10001
- cve.org/CVERecord?id=CVE-2006-10001
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.