HomeWordPress vulnerabilitiesSubscribe to Comments
Subscribe to Comments vulnerabilities
Subscribe to Comments has 3 known vulnerabilities in this database. The most recent published record is dated 19 Jul 2025.
- Known vulnerabilities
- 3
- Active installs
- 10,000+
- Latest version
- 2.3.1
- Last updated
- 29 Oct 2024
- Most recent
- 19 Jul 2025
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| File inclusion CVE-2015-10133 | High 7.2 | Up to 2.1.2 | Fixed in a later version (latest 2.3.1) | 19 Jul 2025 |
| Cross-site scripting (XSS) CVE-2024-8792 | Medium 6.1 | Up to 2.3 | Fixed in a later version (latest 2.3.1) | 30 Oct 2024 |
| Cross-site scripting (XSS) CVE-2006-10001 | Low 3.5 | Before 2.0.8 | Fixed in 2.0.8 | 5 Mar 2023 |
Read the published descriptions
- CVE-2015-10133, 19 Jul 2025
- 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 value. This allows authenticated attackers, with administrative privileges and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. This same function can also be used to execute arbitrary PHP code. CVE record
- CVE-2024-8792, 30 Oct 2024
- The Subscribe to Comments plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the URL in all versions up to, and including, 2.3. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. CVE record
- CVE-2006-10001, 5 Mar 2023
- 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 record
What to do if you run Subscribe to Comments
If you run Subscribe to Comments, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Subscribe to Comments vulnerabilities
Free. We email you when a new vulnerability is published for Subscribe to Comments, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.