CVE-2025-24769
BaseFortify
Publication date: 2025-06-27
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-98 | The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Local File Inclusion (LFI) issue in the WordPress Zenny theme up to version 1.7.5. It allows unauthenticated attackers to include and display local files from the target website by exploiting improper control of filenames in PHP include/require statements. This can expose sensitive information such as database credentials and potentially lead to a complete database takeover. [1]
How can this vulnerability impact me? :
The vulnerability can allow attackers to access and display sensitive local files on your website without authentication. This exposure can lead to the disclosure of critical information like database credentials, which may result in a full database takeover. The high CVSS score of 8.1 indicates a significant risk and a strong likelihood of widespread exploitation, potentially compromising your website's confidentiality, integrity, and availability. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for attempts to exploit the Local File Inclusion (LFI) flaw in the WordPress Zenny theme. Since the vulnerability allows unauthenticated attackers to include local files, you can look for suspicious HTTP requests containing include or require parameters with file paths. Using web server logs, you can grep for patterns such as 'include=' or 'require=' in URLs. For example, commands like `grep -i 'include=' /var/log/apache2/access.log` or `grep -i 'require=' /var/log/nginx/access.log` can help identify potential exploit attempts. Additionally, deploying the Patchstack virtual patch can help block attack attempts and provide logs of blocked requests for detection purposes. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the Patchstack virtual patch (vPatch) released for this vulnerability, which blocks attack attempts until an official fix is available. Since no official patch or fixed version currently exists, using this virtual patch is the recommended way to protect affected sites immediately. Additionally, users should monitor their websites for signs of compromise and consider engaging professional incident response services if a breach is suspected. It is also advisable to keep backups and restrict access to sensitive files where possible. [1]