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

CVE-2025-62868

HIGH · 8.1 CVSS v3.1 Published 2025-10-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Edge CPT allows PHP Local File Inclusion.This issue affects Edge CPT: from n/a through 1.4.

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

A PHP Local File Inclusion (LFI) vulnerability in Edge-Themes Edge CPT (versions up to 1.4) allows attackers to include arbitrary local files due to improper control of filename parameters in include/require statements. This can lead to exposure of sensitive system files, source code disclosure, and potentially remote code execution when combined with other vectors.

MitigationImplement strict input validation and allowlisting for file inclusion paths; upgrade to a patched version if available; disable PHP allow_url_include; ensure all user-supplied input is sanitized before use in include/require functions.

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 checks

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

  1. Verify Edge CPT plugin is installed
    Check your WordPress or CMS plugins directory for a folder named 'edge-cpt', 'edge CPT', or similar naming convention used by Edge-Themes. On the command line: find /path/to/plugins -type d -iname '*edge*cpt*' 2>/dev/null
    Affected if The Edge CPT plugin directory exists on the system
  2. Determine installed version
    Locate the main plugin file (often index.php, main.php, or plugin-name.php inside the plugin folder) and inspect the header comments for the Version field, or check a version/config file if present
    Affected if The reported version is 1.4 or lower (any version 'up to 1.4')
  3. Identify file inclusion code paths
    Search the plugin source code for include, require, include_once, or require_once statements that incorporate variable input. Run: grep -rn 'include\|require' /path/to/edge-cpt/ | grep -E '\$[a-zA-Z_]'
    Affected if The codebase contains include/require statements using dynamic variables without proper sanitization
  4. Check for user input in inclusion functions
    Review files identified in step 3 for $_GET, $_POST, $_REQUEST, or other user-supplied parameters being used directly in include/require paths. Look for patterns like: include($_GET['file']); or require($path . $_REQUEST['filename']);
    Affected if User-controlled parameters are passed directly to include/require functions without validation
  5. Confirm vulnerability trigger is accessible
    If the vulnerable code is in an admin or frontend file, verify the endpoint is accessible (no authentication required for unauthenticated LFI, or check if the affected module is enabled). Test if direct access to suspected vulnerable files returns expected output.
    Affected if The vulnerable file inclusion code can be reached without proper access controls blocking it

If Edge CPT version 1.4 or lower is installed AND the plugin contains include/require statements using unsanitized user input that is accessible, the environment is affected by CVE-2025-62868.

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

Implement strict input validation and allowlisting for file inclusion paths; upgrade to a patched version if available; disable PHP allow_url_include; ensure all user-supplied input is sanitized before use in include/require functions.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62868 — 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-2025-62868 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