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-22377: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in AncoraThemes Saveo

0
High
VulnerabilityCVE-2026-22377cvecve-2026-22377
Published: Fri Feb 20 2026 (02/20/2026, 15:47:05 UTC)
Source: CVE Database V5
Vendor/Project: AncoraThemes
Product: Saveo

Description

CVE-2026-22377 is a vulnerability in the AncoraThemes Saveo WordPress theme, allowing improper control of filenames used in PHP include or require statements. This flaw leads to a Local File Inclusion (LFI) vulnerability, enabling attackers to include and execute arbitrary files on the server. The affected versions are Saveo up to and including 1. 1. 2. Exploitation does not require authentication but may require user interaction depending on deployment. No known public exploits have been reported yet. This vulnerability can lead to unauthorized disclosure of sensitive information, code execution, and potential full system compromise. Organizations using the Saveo theme should prioritize patching or mitigating this issue. Countries with significant WordPress usage and where AncoraThemes products are popular are at higher risk.

AI-Powered Analysis

AILast updated: 02/20/2026, 21:55:19 UTC

Technical Analysis

CVE-2026-22377 identifies a Local File Inclusion (LFI) vulnerability in the AncoraThemes Saveo WordPress theme, specifically versions up to 1.1.2. The vulnerability arises from improper control of the filename parameter used in PHP include or require statements. This flaw allows an attacker to manipulate the input to these statements, causing the server to include unintended local files. By exploiting this, an attacker can read sensitive files such as configuration files, password files, or even execute arbitrary PHP code if they can upload or control files on the server. The vulnerability is classified as a PHP Remote File Inclusion type but is technically a Local File Inclusion since it involves local files. No CVSS score has been assigned yet, and no public exploits have been reported. The vulnerability was reserved in early January 2026 and published in February 2026. The lack of patch links suggests that either patches are pending or users must upgrade to a fixed version once available. This vulnerability is critical in web environments where the Saveo theme is deployed, as it can lead to server compromise, data leakage, and further exploitation.

Potential Impact

The impact of CVE-2026-22377 is significant for organizations using the AncoraThemes Saveo WordPress theme. Successful exploitation can lead to disclosure of sensitive information such as database credentials, configuration files, and user data. Attackers may also execute arbitrary code, leading to full server compromise, defacement, or use of the server as a pivot point for further attacks. This threatens confidentiality, integrity, and availability of affected systems. The vulnerability can disrupt business operations, damage reputation, and lead to regulatory compliance issues. Since WordPress powers a large portion of websites globally, and themes like Saveo are widely used, the scope of affected systems can be broad. Organizations with public-facing WordPress sites are particularly at risk, especially if they have not updated or mitigated this vulnerability.

Mitigation Recommendations

To mitigate CVE-2026-22377, organizations should immediately check if they are using the AncoraThemes Saveo theme version 1.1.2 or earlier and plan to upgrade to a patched version once released. In the absence of an official patch, users should apply the following mitigations: 1) Restrict file inclusion paths by implementing strict input validation and sanitization on parameters controlling include/require statements. 2) Employ Web Application Firewalls (WAFs) with rules to detect and block LFI attempts targeting Saveo theme endpoints. 3) Harden PHP configurations by disabling dangerous functions such as allow_url_include and enabling open_basedir restrictions to limit accessible directories. 4) Monitor web server and application logs for suspicious file inclusion attempts. 5) Limit file permissions on the server to prevent unauthorized file uploads or modifications. 6) Conduct regular security audits and vulnerability scans focusing on WordPress themes and plugins. These steps reduce the attack surface and help detect exploitation attempts before they cause damage.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

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

Threat ID: 6998ca02be58cf853bab9347

Added to database: 2/20/2026, 8:54:26 PM

Last enriched: 2/20/2026, 9:55:19 PM

Last updated: 2/21/2026, 4:01:45 AM

Views: 2

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