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

CVE-2026-25457

HIGH · 8.1 CVSS v3.1 Published 2026-03-25
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 Select-Themes Mixtape mixtape allows PHP Local File Inclusion.This issue affects Mixtape: from n/a through <= 2.1.

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 vulnerability exists in the Select-Themes Mixtape theme (version <= 2.1) where user-supplied input is passed to PHP include/require statements without proper validation, allowing attackers to potentially read or execute arbitrary local files on the server.

MitigationUpgrade to a patched version of the Mixtape theme; if unavailable, implement strict input validation on all parameters used in include/require statements and ensure allow_url_include is disabled.

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. Identify Mixtape theme installation
    Locate the theme files - the Mixtape theme by Select-Themes is typically found in wp-content/themes/mixtape/ or similar WordPress themes directory. Check for a style.css file containing 'Theme Name: Mixtape' or 'Template: mixtape'.
    Affected if The Mixtape theme by Select-Themes is present in the themes directory.
  2. Check theme version
    Open the theme's style.css or functions.php file and locate the version declaration, typically in the file header as 'Version: x.x' or defined as a constant. Compare the version number to 2.1.
    Affected if The installed version is 2.1 or lower.
  3. Inspect include/require statements
    Search all PHP files in the theme directory for include, include_once, require, or require_once statements that use variables or parameters directly, such as 'include($variable)' or 'require($_GET["param"])'. Use grep or a text editor to find these patterns.
    Affected if User-controllable parameters (GET, POST, COOKIE, or REQUEST) are being passed directly to PHP include/require functions without sanitization.
  4. Identify vulnerable parameters
    Review the code found in step 3 to identify which parameters are used in include/require statements. Trace these parameters back to their source (URL parameters, form inputs, etc.) to confirm they accept user input.
    Affected if Parameters used in include/require statements accept direct user input without validation or allow_path validation.
  5. Test parameter behavior
    If the vulnerable parameter is identified (commonly named things like 'file', 'page', 'template', 'path', 'include', or similar), attempt to access a known local file via the URL parameter, such as ?param=../../../../etc/passwd, observing whether the file contents are returned.
    Affected if The server returns contents of arbitrary local files when manipulating the include/require parameter, confirming the LFI vulnerability is exploitable.

A user is affected if the Mixtape theme version 2.1 or lower is installed and contains PHP include/require statements that accept unsanitized user input, allowing arbitrary file access.

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

Upgrade to a patched version of the Mixtape theme; if unavailable, implement strict input validation on all parameters used in include/require statements and ensure allow_url_include is disabled.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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