The Subscribe to Comments for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 2
Description
The Subscribe to Comments for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 2
AI Analyst Comment
Remediation
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
Description Summary:
The Subscribe to Comments WordPress plugin is vulnerable to Local File Inclusion via the Path to header value, allowing authenticated administrators to execute arbitrary PHP code on the server.
Executive Summary:
A high-severity Local File Inclusion vulnerability in the Subscribe to Comments WordPress plugin allows authenticated administrative users to achieve remote code execution.
Vulnerability Details
CVE-ID: CVE-2015-10133
Affected Software: Mark Jaquith Subscribe to Comments
Affected Versions: 0 through 2.1.2
Vulnerability: This is a Local File Inclusion (CWE-98) flaw triggered via the Path to header value. The vulnerability requires the attacker to possess administrative privileges, which are then used to include and execute arbitrary files on the host server.
Business Impact
Successful exploitation of this vulnerability allows an attacker with administrative access to execute arbitrary PHP code on the underlying server. This results in a total compromise of the application, potentially leading to unauthorized data exfiltration, the installation of backdoors, and complete loss of system integrity. With a CVSS score of 7.2, the impact is substantial for any organization relying on this plugin for comment management.
Remediation Plan
Immediate Action: Update the Subscribe to Comments plugin to the latest available version beyond 2.1.2 or remove the plugin from the environment entirely if it is no longer required.
Proactive Monitoring: Review web server access logs for anomalous requests to the plugin directory or suspicious header values that deviate from standard traffic patterns.
Compensating Controls: Implement a Web Application Firewall (WAF) rule to inspect and block malicious input within HTTP headers, specifically targeting directory traversal or file inclusion patterns.
Exploitation Status
Public Exploit Available: Yes, a Metasploit module is available.
Analyst Notes: As of July 21, 2025, there is no public information indicating active exploitation in the wild; however, the presence of a Metasploit module confirms that the vulnerability is weaponized and trivial to exploit for those with the required administrative access.
Analyst Recommendation
Given the severity of potential remote code execution, administrators must prioritize the update or removal of the affected plugin immediately. Failure to remediate this vulnerability leaves the WordPress installation susceptible to total system compromise by any user with administrative permissions.