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-22423: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in Select-Themes SetSail

0
Unknown
VulnerabilityCVE-2026-22423cvecve-2026-22423
Published: Thu Mar 05 2026 (03/05/2026, 05:53:38 UTC)
Source: CVE Database V5
Vendor/Project: Select-Themes
Product: SetSail

Description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Select-Themes SetSail setsail allows PHP Local File Inclusion.This issue affects SetSail: from n/a through <= 1.8.

AI-Powered Analysis

AILast updated: 03/05/2026, 09:03:09 UTC

Technical Analysis

CVE-2026-22423 is a Local File Inclusion (LFI) vulnerability found in the Select-Themes SetSail PHP theme, affecting versions up to 1.8. The vulnerability arises from improper control over the filename parameter used in PHP include or require statements, allowing an attacker to manipulate the input to include arbitrary local files on the server. This can lead to unauthorized disclosure of sensitive files such as configuration files, source code, or credentials, and potentially enable remote code execution if combined with other vulnerabilities or writable file uploads. The issue is classified as a PHP Remote File Inclusion type but specifically manifests as Local File Inclusion due to improper input validation. The vulnerability was reserved in early 2026 and published in March 2026, with no CVSS score assigned yet and no known exploits in the wild. The lack of authentication requirement and the ability to influence file inclusion make this vulnerability particularly dangerous in shared hosting or multi-user environments. The affected product, SetSail, is a WordPress theme developed by Select-Themes, commonly used in various websites, which increases the attack surface. The vulnerability underscores the importance of secure coding practices around file inclusion functions in PHP, such as whitelisting allowed files, sanitizing inputs, and avoiding dynamic inclusion of files based on user input.

Potential Impact

The primary impact of CVE-2026-22423 is the potential unauthorized disclosure of sensitive information stored on the server, including configuration files, credentials, and source code. This can lead to further attacks such as privilege escalation, remote code execution, or complete system compromise if attackers leverage the disclosed information. The vulnerability undermines the confidentiality and integrity of affected systems. For organizations, this can result in data breaches, service disruptions, reputational damage, and compliance violations. Since the vulnerability does not require authentication or user interaction, it can be exploited remotely by unauthenticated attackers, increasing the risk. Websites using the vulnerable SetSail theme are at risk of being compromised, which can affect e-commerce, content management, and other web services relying on this theme. The scope of affected systems is limited to those running the vulnerable versions of SetSail, but given the popularity of PHP and WordPress themes, the potential impact is significant.

Mitigation Recommendations

1. Immediately audit all instances of the SetSail theme and identify versions up to 1.8 in use. 2. Apply patches or updates from Select-Themes as soon as they are released addressing this vulnerability. 3. Implement strict input validation and sanitization on all parameters influencing file inclusion, ideally using whitelists of allowed files. 4. Disable dynamic file inclusion based on user input where possible. 5. Configure PHP settings to disable dangerous functions like allow_url_include and restrict file system access using open_basedir. 6. Employ Web Application Firewalls (WAFs) with rules to detect and block attempts to exploit LFI vulnerabilities. 7. Regularly monitor logs for suspicious file inclusion attempts or unusual access patterns. 8. Educate developers on secure coding practices related to file inclusion and input handling. 9. Consider isolating or sandboxing web applications to limit the impact of potential exploitation. 10. Backup critical data regularly to enable recovery in case of compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

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

Threat ID: 69a92045d1a09e29cbe6979a

Added to database: 3/5/2026, 6:18:45 AM

Last enriched: 3/5/2026, 9:03:09 AM

Last updated: 3/5/2026, 3:02:27 PM

Views: 4

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses