CVE-2026-25380
Local File Inclusion in Feedy Plugin Allows Code Execution
Publication date: 2026-03-25
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jwsthemes | feedy | to 2.1.5 (exc) |
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 an improper control of filename for include/require statements in the PHP program called jwsthemes Feedy feedy. It is a PHP Local File Inclusion vulnerability, which means that an attacker can manipulate the filename used in include or require statements to include unintended local files on the server.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to include and execute arbitrary local files on the server running the vulnerable Feedy application. This can lead to unauthorized access to sensitive information, code execution, or other malicious actions depending on the included files.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This Local File Inclusion (LFI) vulnerability in the WordPress Feedy Theme allows unauthenticated attackers to access sensitive files, including database credentials. Such exposure can lead to a full database compromise, potentially resulting in unauthorized access to personal or protected data.
The compromise of sensitive data due to this vulnerability could lead to violations of data protection regulations such as GDPR and HIPAA, which require strict controls to protect personal and health information. Failure to secure such data may result in non-compliance, legal penalties, and reputational damage.
Therefore, organizations using affected versions of the Feedy Theme should urgently apply patches or mitigations to maintain compliance with these common standards and regulations.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the CVE-2026-25380 vulnerability, you should immediately update the WordPress Feedy Theme to version 2.1.5 or later, where the vulnerability is patched.
If updating immediately is not possible, apply Patchstack’s mitigation rules which are designed to block exploitation attempts against this Local File Inclusion vulnerability.
Due to the high severity and likelihood of mass exploitation campaigns, prioritizing these mitigation steps is critical to protect sensitive information and prevent potential full database compromise.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
CVE-2026-25380 is a Local File Inclusion (LFI) vulnerability in the WordPress Feedy Theme versions prior to 2.1.5 that allows unauthenticated attackers to include and display local files. Detection typically involves monitoring for suspicious HTTP requests attempting to exploit the LFI, such as requests containing file path traversal patterns or attempts to include sensitive files.
To detect exploitation attempts on your web server logs, you can search for requests with suspicious parameters that include file paths or traversal sequences like "../".
- Use grep or similar tools on your web server access logs to find suspicious requests, for example:
- grep -iE "(\.{2}/|etc/passwd|boot.ini|\?file=)" /var/log/apache2/access.log
- Check for unusual PHP include or require statements in logs or application monitoring tools.
- Use web application firewall (WAF) logs or mitigation rules provided by Patchstack to detect and block exploitation attempts.
Ultimately, updating the Feedy Theme to version 2.1.5 or later is the recommended mitigation to prevent exploitation.