Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-22368: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in axiomthemes Redy

0
High
VulnerabilityCVE-2026-22368cvecve-2026-22368
Published: Fri Feb 20 2026 (02/20/2026, 15:47:03 UTC)
Source: CVE Database V5
Vendor/Project: axiomthemes
Product: Redy

Description

CVE-2026-22368 is a high-severity vulnerability affecting the axiomthemes Redy product up to version 1. 0. 2. It involves improper control of filenames used in PHP include/require statements, leading to a Remote File Inclusion (RFI) vulnerability. This flaw allows an attacker to include and execute remote malicious PHP code on the affected server without authentication or user interaction. The vulnerability has a CVSS score of 8. 1, reflecting its critical impact on confidentiality, integrity, and availability. Although no known exploits are currently reported in the wild, the vulnerability poses a significant risk to websites using the Redy theme. Organizations running vulnerable versions should prioritize patching or applying mitigations to prevent potential remote code execution attacks. Countries with widespread use of PHP-based CMS and WordPress themes, including the United States, Germany, India, Brazil, and Russia, are at higher risk.

AI-Powered Analysis

AILast updated: 02/20/2026, 20:56:40 UTC

Technical Analysis

CVE-2026-22368 is a Remote File Inclusion (RFI) vulnerability found in the axiomthemes Redy WordPress theme, affecting versions up to and including 1.0.2. The vulnerability arises due to improper validation and control of filenames passed to PHP include or require statements. This flaw enables an attacker to supply a crafted URL or file path, causing the application to include and execute arbitrary remote PHP code. RFI vulnerabilities are particularly dangerous because they allow remote attackers to execute code on the server without authentication or user interaction, potentially leading to full system compromise. The CVSS 3.1 base score of 8.1 indicates high severity, with network attack vector, high complexity, no privileges required, and no user interaction needed. The impact includes complete loss of confidentiality, integrity, and availability of the affected system. Although no public exploits have been reported yet, the vulnerability is publicly disclosed and should be considered exploitable. The lack of available patches at the time of disclosure increases the urgency for organizations to implement temporary mitigations or upgrade once fixes are released. This vulnerability is particularly relevant for websites using the Redy theme, which is built on PHP and commonly deployed in WordPress environments.

Potential Impact

The exploitation of CVE-2026-22368 can lead to remote code execution on affected web servers, allowing attackers to take full control over the compromised system. This can result in data theft, website defacement, installation of backdoors, pivoting to internal networks, and disruption of services. Organizations relying on the Redy theme for their websites risk exposure of sensitive customer data, intellectual property, and operational disruption. The vulnerability's network accessibility and lack of authentication requirements make it highly attractive to attackers, increasing the likelihood of exploitation once public exploits emerge. The impact extends beyond individual websites to potentially affect entire hosting environments and connected infrastructure. Given the widespread use of PHP-based CMS platforms globally, the threat has broad implications for web security and trust.

Mitigation Recommendations

1. Immediately upgrade the Redy theme to a version that addresses this vulnerability once available from the vendor. 2. If patches are not yet released, implement web application firewall (WAF) rules to block suspicious requests containing remote file inclusion patterns or unexpected URL parameters. 3. Disable allow_url_include and allow_url_fopen directives in the PHP configuration to prevent remote file inclusion. 4. Conduct code reviews to identify and sanitize all user inputs used in include/require statements, enforcing strict validation and whitelisting. 5. Restrict file permissions and isolate web server processes to minimize the impact of potential exploitation. 6. Monitor web server logs for unusual requests or errors indicative of attempted exploitation. 7. Employ runtime application self-protection (RASP) tools to detect and block malicious code execution attempts. 8. Educate development and operations teams about secure coding practices related to file inclusion and PHP configuration hardening.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2026-01-07T12:21:29.302Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6998c9e1be58cf853bab6ac0

Added to database: 2/20/2026, 8:53:53 PM

Last enriched: 2/20/2026, 8:56:40 PM

Last updated: 2/21/2026, 6:28:20 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

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

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats