CVE-2025-69050
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 Edge-Themes Overworld overworld allows PHP Local File Inclusion.This issue affects Overworld: from n/a through <= 1.3.
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 confidenceA Local File Inclusion (LFI) vulnerability in the Edge-Themes Overworld theme allows attackers to manipulate PHP include/require statements to execute arbitrary local PHP files. This occurs due to insufficient validation of user-controlled input used in file path arguments, potentially enabling remote code execution.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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.
-
Confirm Overworld theme installationSearch for the Overworld theme directory in the site's theme folder (commonly wp-content/themes/overworld or similar path depending on the CMS/platform). List all PHP files within the theme.Affected if The Overworld theme is present on the system.
-
Locate file inclusion codeSearch theme PHP files for patterns: include($_GET[...]), require($_REQUEST[...]), include_once($_POST[...]) or similar dynamic file inclusion using user-supplied input arrays.Affected if Any PHP file in the theme uses $_GET, $_POST, or $_REQUEST variables directly in include, require, include_once, or require_once statements.
-
Inspect the vulnerable inclusion pointExamine the identified file inclusion code to determine if user-controlled input (such as a 'page', 'template', or 'file' parameter from query strings) flows directly to the include/require function without sanitization.Affected if User input from request parameters is passed to include/require without validation like basename(), realpath(), or allowlist checking.
-
Check for path traversal patternsReview the inclusion code for characters like '../' or absolute path prefixes in the input parameter. Determine if the code allows navigating outside the intended theme directory.Affected if The code permits path traversal sequences or does not restrict the inclusion to a specific allowed directory.
If the Overworld theme is installed and contains PHP files that directly use unsanitized user input in include/require statements, the environment is likely affected by this LFI vulnerability.
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 dataImplement strict allowlist-based validation for file inclusion paths and disable remote file inclusion in PHP configuration (allow_url_include=0). Replace dynamic file inclusion with a whitelist of permitted files.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69050 — 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-2025-69050 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