CVE-2026-57793
Deferred Deferred - Pending Action

PHP Local File Inclusion in Elated-Themes Flow

Vulnerability report for CVE-2026-57793, 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 Elated-Themes Flow flow allows PHP Local File Inclusion.This issue affects Flow: from n/a through <= 1.8.

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 2 associated CPEs
Vendor Product Version / Range
elated_themes flow to 1.8 (inc)
elated-themes flow From 1.0 (inc) to 1.8 (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

The WordPress Flow Theme, versions 1.8 and below, contains a Local File Inclusion (LFI) vulnerability. This means that an attacker can exploit improper control of filenames used in include or require statements in PHP, allowing them to include local files on the target website.

This vulnerability arises from the theme's PHP code not properly validating or sanitizing the filename input, which can lead to unauthorized access to sensitive files on the server.

Detection Guidance

Detecting the PHP Local File Inclusion (LFI) vulnerability in the Elated-Themes Flow theme (versions <= 1.8) on your system or network involves checking for the presence of the vulnerable theme and testing for the vulnerability. Below are some methods and commands to help identify this issue.

  • Check if the Flow theme is installed on your WordPress site. Navigate to the WordPress admin dashboard, go to 'Appearance' > 'Themes', and look for the Flow theme. Note the version number if it is installed.
  • Verify the theme version via the filesystem. Run the following command to check the theme's version in the WordPress themes directory: 'grep -i 'Version' /path/to/wordpress/wp-content/themes/flow/style.css'. Replace '/path/to/wordpress' with the actual path to your WordPress installation.
  • Use a vulnerability scanner like WPScan to detect the vulnerable theme. Run the following command: 'wpscan --url your-wordpress-site.com --enumerate vp,vt,tt'. This will scan for vulnerable plugins, themes, and timthumb files.
  • Manually test for LFI by attempting to access sensitive files via the vulnerable parameter. For example, if the theme uses a parameter like 'file' or 'template', try accessing local files such as: 'http://your-wordpress-site.com/?file=../../../../wp-config.php'. Note that this should only be done in a controlled environment with permission, as it may expose sensitive data.
  • Review web server logs for suspicious activity, such as requests containing '../' or other path traversal patterns. Use commands like 'grep -r '\.\./' /var/log/apache2/' or 'grep -r '\.\./' /var/log/nginx/' to search for such patterns in your logs.

If the Flow theme is detected and its version is 1.8 or below, your system is vulnerable. Immediate action, such as updating or replacing the theme, is recommended.

Impact Analysis

Exploiting this Local File Inclusion vulnerability could allow attackers to access sensitive data such as database credentials.

Depending on the server configuration, attackers might achieve a complete database takeover, leading to severe confidentiality, integrity, and availability impacts on your website.

Since the theme has not been updated in over a year and is unlikely to be patched officially, the risk remains unless mitigated by other means.

Compliance Impact

This vulnerability, a PHP Local File Inclusion (LFI) in the Flow theme, can significantly impact compliance with standards and regulations like GDPR and HIPAA.

  • GDPR: The vulnerability may expose sensitive personal data stored in local files, such as database credentials or user information. Under GDPR, organizations must protect personal data from unauthorized access. A breach resulting from this vulnerability could lead to non-compliance, triggering fines and mandatory breach notifications.
  • HIPAA: If the affected system processes or stores protected health information (PHI), this vulnerability could lead to unauthorized access to PHI. HIPAA requires strict safeguards for PHI, and exploitation of this flaw may constitute a breach, resulting in penalties and corrective action plans.

Additionally, the lack of official patches for the theme increases the risk of prolonged exposure, further complicating compliance efforts. Organizations must take immediate remediation steps, such as replacing the theme or deploying mitigation rules, to avoid regulatory violations.

Mitigation Strategies

Immediate action is recommended to mitigate the Local File Inclusion vulnerability in the WordPress Flow Theme versions 1.8 and below.

  • Update the theme to a newer, patched version if available.
  • Replace the vulnerable theme entirely if no update is available.
  • Note that simply deactivating the theme does not fully mitigate the threat.
  • Deploy a Patchstack mitigation rule to help protect against exploitation.

Chat Assistant

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

EPSS Chart