dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2026-57800

HIGH · 7.5 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click 5 weeks old

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Edge-Themes Overworld overworld allows PHP Local File Inclusion.This issue affects Overworld: from n/a through <= 1.5.

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 · moderate confidence

The Overworld theme by Edge-Themes contains a Local File Inclusion (LFI) vulnerability where user-supplied input is improperly validated before being used in PHP include/require statements. This allows attackers to include arbitrary local PHP files, potentially leading to remote code execution.

MitigationUpdate to a patched version of the Overworld theme; until available, implement strict input validation and whitelist-based file inclusion controls in the theme's PHP code.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Overworld theme installation
    Check your web server's theme directory (commonly /wp-content/themes/overworld/ or similar path depending on your CMS/framework) for the presence of the Overworld theme by Edge-Themes.
    Affected if The Overworld theme directory exists on the server.
  2. Identify installed theme version
    Open the theme's style.css file or theme.json in the Overworld theme directory and locate the Version: header. Compare this version number against the official Edge-Themes release notes to determine if a patched version exists.
    Affected if The installed version predates the patched release from Edge-Themes.
  3. Find vulnerable file inclusion code
    Search the theme's PHP files (particularly in the root and includes/ directories) for patterns like 'include(', 'require(', 'include_once(', or 'require_once(' where the path parameter contains $_GET, $_POST, or $_REQUEST variables without proper sanitization. Common vulnerable patterns include: include($_GET['file']); or require($theme_path . $_REQUEST['template']);
    Affected if PHP files contain include/require statements using unsanitized user input from $_GET, $_POST, or $_REQUEST.
  4. Identify the vulnerable parameter
    Examine the identified vulnerable code to determine which URL parameter controls the file inclusion (for example, 'file', 'template', 'page', or 'path'). Test accessing the affected page with a benign LFI probe (e.g., ?param=../../../../etc/passwd or ?param=../../../../windows/win.ini) using a safe read-only test.
    Affected if The parameter accepts path traversal sequences and returns file contents from the server.
  5. Check for exploitation indicators
    Review web server access logs (apache2/access.log, nginx/access.log, or similar) for suspicious requests containing path traversal patterns (../../) targeting the vulnerable parameter, especially with .php extensions or system file paths.
    Affected if Logs show requests with path traversal aimed at the file inclusion parameter, or unexpected PHP files have been created/modified on the server.

You are affected if the Overworld theme is installed, the version is older than the patched release, and the vulnerable file inclusion code with unsanitized user input is present and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the Overworld theme; until available, implement strict input validation and whitelist-based file inclusion controls in the theme's PHP code.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57800 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57800 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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