CVE-2025-47474
BaseFortify
Publication date: 2026-01-22
Last updated on: 2026-04-27
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ninetheme | anarkali | From 1.0.0 (inc) to 1.0.9 (inc) |
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?
CVE-2025-47474 is a Local File Inclusion (LFI) vulnerability in the WordPress Anarkali Theme up to version 1.0.9. It allows unauthenticated attackers to include and display local files from the target website by exploiting improper control of filename in PHP include/require statements. This can expose sensitive information such as database credentials and potentially lead to a complete database takeover depending on the website's configuration. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers to access and display sensitive local files on your website, including database credentials. Exploiting this flaw could lead to a complete database takeover, compromising the confidentiality, integrity, and availability of your data and systems. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this Local File Inclusion (LFI) vulnerability can be done by monitoring web requests for suspicious patterns that attempt to include local files. You can look for HTTP requests containing parameters with file paths or traversal sequences (e.g., ../). Commands such as using curl or wget to test URL parameters for file inclusion attempts can help. For example, you might run: curl "http://targetsite.com/?page=../../../../etc/passwd" to see if the server includes local files. Additionally, web application firewalls (WAFs) with rules targeting LFI patterns can help detect exploitation attempts. Patchstack has issued a mitigation rule that can also help in detecting and blocking attacks exploiting this vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the Patchstack mitigation rule designed to block attacks exploiting this vulnerability until an official patch is released. It is also recommended to restrict file inclusion functionality in the PHP configuration, validate and sanitize all user inputs, and implement a web application firewall (WAF) with rules to detect and block LFI attempts. Monitoring logs for suspicious activity and limiting file permissions on the server can further reduce risk. Since no official fix is available as of the publication date, these mitigations are critical to protect affected websites. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can lead to unauthorized access and exposure of sensitive information such as database credentials, which may result in data breaches. Such breaches can compromise compliance with data protection regulations like GDPR and HIPAA, as these standards require safeguarding sensitive data against unauthorized access and ensuring data confidentiality and integrity. [1]