CVE-2026-57793
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceLocal File Inclusion (LFI) vulnerability in Elated-Themes Flow theme allows attackers to manipulate file inclusion parameters to include arbitrary PHP files from the server, potentially leading to remote code execution. The vulnerability stems from improper validation of user-supplied input in PHP include/require statements.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Flow theme is installedInspect the theme directory (typically wp-content/themes/flow or similar path depending on CMS) and look for theme declaration files (style.css, functions.php) containing 'Elated Themes' and 'Flow' branding.Affected if The Flow theme by Elated-Themes is present in the environment.
-
Determine Flow theme versionOpen the theme's style.css or functions.php file and locate the version comment or variable (e.g., 'Version: x.x.x'). Compare this version against any known affected version range.Affected if The installed version falls within an affected version range (if such a range becomes known).
-
Search for vulnerable include/require patternsExamine PHP files in the theme for dynamic file inclusion statements that use user-supplied parameters (e.g., include($_GET['file']); require($_REQUEST['path']);). Look for patterns like include($var) or require_once($param).Affected if The theme contains include/require statements that directly use $_GET, $_POST, or $_REQUEST variables without sanitization.
-
Identify exposed file inclusion parametersReview application routing, AJAX endpoints, or theme template files to identify URL parameters (such as 'file', 'path', 'template', 'page', 'include') that control which files are loaded.Affected if URL parameters that control file inclusion are accessible and not protected by CSRF tokens or authentication.
-
Check PHP allow_url_include settingCreate a PHPinfo page or check php.ini for the directive 'allow_url_include'. If enabled, remote file inclusion becomes possible in addition to local file inclusion.Affected if allow_url_include is set to On in PHP configuration (this worsens the impact but is not required for LFI).
A user is affected if the Elated-Themes Flow theme is installed with vulnerable include/require code paths that accept unsanitized user input to control which files are loaded on the server.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to the latest version of Flow theme if a patch is available; otherwise, implement strict whitelist-based input validation on all file inclusion parameters and disable allow_url_include in PHP configuration.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57793 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57793 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data