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

CVE-2025-5804

HIGH · 7.5 CVSS v3.1 Published 2026-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 Case Themes Case Theme User case-theme-user allows PHP Local File Inclusion.This issue affects Case Theme User: from n/a through < 1.0.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 · high confidence

A PHP Local File Inclusion vulnerability exists in the Case Theme User theme where user-supplied input is used in include/require statements without proper validation or sanitization. This allows unauthenticated attackers to include arbitrary local PHP files, potentially exposing sensitive configuration data or achieving code execution.

MitigationUpdate to version 1.0.4 or later which contains the vendor fix. If immediate update is not possible, disable the theme or restrict access to the vulnerable endpoint at the web server level.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 if Case Theme User is installed
    Search your web server document root for directories or files containing 'case-theme-user' or 'case-theme' in the path. Check wp-content/themes/ for WordPress installations or common theme directories for other PHP applications.
    Affected if The Case Theme User theme directory exists in your web root or CMS theme folder.
  2. Determine the installed theme version
    Look for a version file, style.css with version header, or a readme/changelog file within the theme directory. Check the theme's main PHP file for a version constant or comment.
    Affected if The theme version is found to be lower than 1.0.4 or no version identifier above 1.0.3 is present.
  3. Locate the vulnerable include/require pattern
    Search the theme's PHP files for include(), require(), include_once(), or require_once() statements where variables from $_GET, $_POST, or $_REQUEST are used directly in the file path without sanitization. Focus on files handling page templates or routing.
    Affected if You find include/require statements using unsanitized user input like include($_GET['page']) or similar patterns without validation functions.
  4. Verify the vulnerable endpoint is accessible
    Test accessing common entry points of the theme (index.php, functions.php, or routing files) with a crafted request that includes a local file path, such as ?page=../../wp-config.php or similar path traversal attempts.
    Affected if The server returns content from the requested local PHP file or reveals file contents indicating the LFI is exploitable.

Your environment is affected if the Case Theme User theme is installed with a version below 1.0.4 and the LFI vulnerability in include/require statements 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.0.4 or later which contains the vendor fix. If immediate update is not possible, disable the theme or restrict access to the vulnerable endpoint at the web server level.

Recommended fix Moderate confidence

Case Theme User version 1.0.4 or later

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Update the Case Theme User plugin to version 1.0.4 or later through the WordPress admin dashboard (Plugins > Add New > Upload or directly from the WordPress plugin repository).
  3. 3. Alternatively, download the latest version from the official WordPress plugin repository or Case Themes website.
  4. 4. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins.
  5. 5. Test that the plugin functionality still works correctly after the update.
  6. 6. Monitor the site for any errors or unusual behavior following the upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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