CVE-2026-22368
Local File Inclusion in Redy ≤ 1.0.2 PHP Component
Publication date: 2026-02-20
Last updated on: 2026-02-20
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| axiomthemes | redy | From 1.0.0 (inc) to 1.0.2 (inc) |
| axiomthemes | redy | to 1.0.2 (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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
Can you explain this vulnerability to me?
CVE-2026-22368 is a Local File Inclusion (LFI) vulnerability found in the WordPress Redy Theme versions up to and including 1.0.2. It occurs due to improper control of filenames used in PHP include or require statements, allowing an attacker to include and display local files from the target website without authentication.
This vulnerability is classified under OWASP Top 10 A3: Injection and can be exploited by an unauthenticated attacker to access sensitive files on the server.
How can this vulnerability impact me? :
Exploitation of this vulnerability can expose sensitive files such as those containing database credentials. This exposure could potentially lead to a complete database takeover depending on the website’s configuration.
Because the vulnerability requires no authentication to exploit, it poses a high risk to affected websites.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability allows an unauthenticated attacker to include and display local files from the target website by exploiting improper control of filename in include/require statements in the Redy WordPress theme.'}, {'type': 'paragraph', 'content': 'To detect attempts to exploit this Local File Inclusion (LFI) vulnerability on your system or network, you can monitor web server logs for suspicious requests that include file path traversal patterns or attempts to include local files.'}, {'type': 'list_item', 'content': 'Use command-line tools like grep to search your web server access logs for suspicious parameters, for example: grep -iE "(\\.|%2e){2,}|include|require" /var/log/apache2/access.log'}, {'type': 'list_item', 'content': 'Look for requests containing typical LFI payloads such as ../../ or attempts to include sensitive files like /etc/passwd or wp-config.php.'}, {'type': 'list_item', 'content': 'Use intrusion detection systems or web application firewalls (WAF) with rules to detect and alert on LFI attack patterns.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Since no official patch is currently available for this vulnerability in the Redy WordPress theme, immediate mitigation is critical.
- Implement the mitigation rule provided by Patchstack that can block attacks targeting this Local File Inclusion vulnerability.
- Restrict access to sensitive files on your server by proper file permissions and web server configuration.
- Monitor your web server logs for suspicious activity and block malicious IP addresses if necessary.
- Consider disabling or removing the vulnerable Redy theme until an official patch is released.