Skip to main content

CVE-2025-47653: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in tggfref WP-Recall

High
VulnerabilityCVE-2025-47653cvecve-2025-47653cwe-98
Published: Wed May 07 2025 (05/07/2025, 14:20:44 UTC)
Source: CVE
Vendor/Project: tggfref
Product: WP-Recall

Description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in tggfref WP-Recall allows PHP Local File Inclusion. This issue affects WP-Recall: from n/a through 16.26.14.

AI-Powered Analysis

AILast updated: 07/05/2025, 08:55:23 UTC

Technical Analysis

CVE-2025-47653 is a high-severity vulnerability classified under CWE-98, which involves improper control of filenames used in include or require statements within PHP programs. Specifically, this vulnerability affects the tggfref WP-Recall plugin, versions up to and including 16.26.14. The flaw allows an attacker to perform PHP Local File Inclusion (LFI), which can lead to remote code execution if exploited correctly. The vulnerability arises because the plugin does not adequately validate or sanitize user-supplied input used in PHP include or require statements, enabling an attacker to manipulate the file path and include arbitrary files from the server. This can result in the disclosure of sensitive information, execution of malicious code, or complete compromise of the web server hosting the vulnerable plugin. The CVSS v3.1 base score is 7.5, indicating a high severity level, with the vector string AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. This means the attack can be performed remotely over the network, requires low privileges, no user interaction, and impacts confidentiality, integrity, and availability to a high degree. Although no known exploits are currently observed in the wild, the vulnerability's nature and impact make it a critical concern for organizations using this plugin. The lack of available patches at the time of publication further increases the urgency for mitigation. Given that WP-Recall is a WordPress plugin, the vulnerability primarily affects websites running WordPress with this specific plugin installed, potentially exposing them to severe compromise.

Potential Impact

For European organizations, the exploitation of this vulnerability could lead to significant operational and reputational damage. Organizations relying on WordPress websites with the WP-Recall plugin may face unauthorized disclosure of sensitive data, including customer information, internal documents, or configuration files. The ability to execute arbitrary PHP code remotely could allow attackers to deploy malware, establish persistent backdoors, or pivot to other internal systems, thereby compromising broader IT infrastructure. This risk is particularly acute for sectors such as finance, healthcare, government, and e-commerce, where data confidentiality and service availability are critical. Additionally, exploitation could lead to website defacement or denial of service, impacting customer trust and business continuity. Given the interconnected nature of European digital services and strict data protection regulations like GDPR, a breach stemming from this vulnerability could also result in regulatory penalties and legal consequences. The high severity and remote exploitability underscore the need for immediate attention to prevent potential widespread impact across European organizations using this plugin.

Mitigation Recommendations

To mitigate this vulnerability effectively, European organizations should first identify all WordPress instances using the WP-Recall plugin, particularly versions up to 16.26.14. Since no official patch is currently available, organizations should consider the following specific actions: 1) Temporarily disable or uninstall the WP-Recall plugin to eliminate the attack surface until a patch is released. 2) Implement Web Application Firewall (WAF) rules to detect and block suspicious requests attempting to exploit file inclusion, focusing on patterns that manipulate include/require parameters. 3) Conduct thorough input validation and sanitization on any custom code interacting with file paths to prevent injection of malicious input. 4) Monitor web server logs for unusual file access patterns or errors indicative of attempted exploitation. 5) Restrict PHP file inclusion paths using PHP configuration directives such as open_basedir to limit accessible directories. 6) Employ principle of least privilege for web server processes to minimize potential damage from code execution. 7) Stay informed about vendor updates and apply patches immediately once available. 8) Perform regular security audits and penetration tests focusing on plugin vulnerabilities. These targeted measures go beyond generic advice by addressing the specific nature of the vulnerability and the operational context of affected systems.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Patchstack
Date Reserved
2025-05-07T10:45:13.130Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682d9819c4522896dcbd8bd6

Added to database: 5/21/2025, 9:08:41 AM

Last enriched: 7/5/2025, 8:55:23 AM

Last updated: 7/26/2025, 8:39:35 PM

Views: 9

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats