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

CVE-2026-28125

HIGH · 8.1 CVSS v3.1 Published 2026-03-05
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 AncoraThemes Midi midi allows PHP Local File Inclusion.This issue affects Midi: from n/a through <= 1.14.

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

Local File Inclusion vulnerability in AncoraThemes Midi theme allows attackers to include arbitrary local files via unsanitized input in PHP include/require statements. The vulnerability stems from improper control of filenames in PHP file inclusion functions, potentially exposing sensitive server files.

MitigationImplement strict input validation using allowlists, avoid dynamic file inclusion with user-supplied data, and use basename() or realpath() functions to sanitize and normalize file paths before inclusion.

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. Locate the AncoraThemes Midi theme installation
    Check your web server's themes directory (commonly /wp-content/themes/ or similar) for a folder named 'midi', 'midi-theme', or similar AncoraThemes Midi theme directory. Search for files like style.css that typically contain theme metadata.
    Affected if The Midi theme by AncoraThemes is not found in the themes directory, meaning the theme is not installed.
  2. Identify the installed Midi theme version
    Open the theme's style.css file or any version file within the Midi theme directory. Look for a comment block or version definition (e.g., 'Version: x.x.x'). Compare the found version against any known affected version ranges provided by the vendor.
    Affected if A version is found and it falls within an affected version range, or no version information is available to confirm the theme is patched.
  3. Find PHP files with dynamic file inclusion functions
    Search the Midi theme directory for PHP files containing 'include', 'require', 'include_once', or 'require_once' followed by variables (e.g., include($var), require $_GET['file']). Use grep or a code search tool across all .php files in the theme folder.
    Affected if Files using dynamic variables in include/require statements are found without proper sanitization.
  4. Examine the file inclusion logic for user input handling
    Review the identified PHP files to determine if the variable passed to include/require originates from user-controlled sources such as $_GET, $_POST, or $_REQUEST parameters. Look for parameters that accept file paths or names.
    Affected if User-supplied input (e.g., ?file=../config.php) reaches the include/require function without validation.
  5. Test if the vulnerable parameter is accessible via HTTP
    Send a request to the web application with a crafted parameter pointing to a local file (e.g., ?file=../../../../../../etc/passwd or ?file=config.php). Observe if the file contents are reflected in the response.
    Affected if The server returns the contents of arbitrary local files, confirming the LFI vulnerability is exploitable.

If the AncoraThemes Midi theme is installed with vulnerable file inclusion code that accepts user input, the environment is affected by CVE-2026-28125.

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 using allowlists, avoid dynamic file inclusion with user-supplied data, and use basename() or realpath() functions to sanitize and normalize file paths before inclusion.

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-28125 — 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-28125 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