Overview
This report highlights the critical security vulnerability, CVE-2025-60150, which impacts the Subscribe to Download plugin on the WordPress platform. This PHP Remote File Inclusion vulnerability can lead to significant breaches, potentially compromising entire systems and leading to severe data leakage. It is crucial to address this issue due to the high-risk score and broad user base of the affected plugin.
Vulnerability Summary
CVE ID: CVE-2025-60150
Severity: High (7.5 CVSS Score)
Attack Vector: Network
Privileges Required: None
User Interaction: Required
Impact: System compromise or data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
Subscribe to Download | n/a through 2.0.9
How the Exploit Works
The vulnerability stems from an improper control of the filename for include/require statements in the PHP program of wpshuffle’s Subscribe to Download plugin. This issue allows for PHP Local File Inclusion (LFI), meaning an attacker can trick the script into including files from remote servers, leading to code execution. This execution could potentially compromise the system or lead to data leakage.
Conceptual Example Code
Below is a conceptual example of how this vulnerability might be exploited. This might be a part of a malicious HTTP request:
GET /wp-content/plugins/subscribe-to-download/download.php?file=../../../../../../../etc/passwd HTTP/1.1
Host: vulnerablewebsite.com
In this example, the attacker is attempting to access the ‘passwd’ file, a common target due to its sensitive data. By manipulating the ‘file’ parameter in the GET request, the attacker can traverse the directory tree to access files outside of the intended directory.
Countermeasures
The best mitigation strategy is to apply the vendor patch as soon as it becomes available. If the patch is not yet available, using a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can provide temporary mitigation. Additionally, disable the plugin if it’s not immediately necessary, until the patch is issued. Regularly monitoring system logs for any unusual activity is also recommended.
