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

CVE-2025-31014

HIGH · 7.5 CVSS v3.1 Published 2025-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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 Hossein Material Dashboard material-dashboard allows PHP Local File Inclusion.This issue affects Material Dashboard: from n/a through <= 1.4.5.

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

Local File Inclusion (LFI) vulnerability in the Hossein Material Dashboard allows attackers to manipulate file inclusion parameters to read sensitive files from the server filesystem. This occurs due to insufficient input validation on include/require statements, potentially exposing configuration files, credentials, or the source code.

MitigationImplement strict whitelist-based validation for file inclusion parameters and disable allow_url_include in PHP configuration. Audit all include/require statements to ensure user-supplied input cannot be used to traverse directories or access unauthorized files.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/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 if Hossein Material Dashboard is installed
    Search the web server document root for files or directories named 'hossein', 'dashboard', 'material', or review web application source code for references to 'Hossein Material Dashboard'. Check framework configuration files or package manifests if available.
    Affected if The application codebase is present on the server.
  2. Locate PHP files using include or require statements
    Search the application source for PHP files containing 'include(', 'require(', 'include_once(', or 'require_once(' followed by variables, such as: include($file), require($_GET['page']), or similar patterns.
    Affected if PHP files with dynamic include/require statements that accept variable input are found.
  3. Verify if include/require parameters accept user input without sanitization
    Examine the identified include/require statements to determine if the variable passed comes directly from $_GET, $_POST, or $_REQUEST parameters without validation, sanitization, or whitelist filtering.
    Affected if User-supplied input from request parameters flows directly into include/require statements without validation.
  4. Test if directory traversal is possible in file inclusion parameters
    Attempt to access known files via the suspected parameter, such as ../../../../etc/passwd or ..\..\..\windows\system32\config\sam, observing if the server returns file contents or error messages revealing file access.
    Affected if The application returns content from files outside the intended directory, indicating traversal is not blocked.

If the Hossein Material Dashboard is deployed and contains PHP include/require statements that use unsanitized user input from request parameters, the environment is affected by this LFI vulnerability.

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

Implement strict whitelist-based validation for file inclusion parameters and disable allow_url_include in PHP configuration. Audit all include/require statements to ensure user-supplied input cannot be used to traverse directories or access unauthorized files.

Recommended fix Moderate confidence

Material Dashboard version 1.4.6 or later

  1. 1. Navigate to the official Material Dashboard repository or releases page to check for the latest version
  2. 2. Look for version 1.4.6 or later which should contain the LFI vulnerability fix
  3. 3. Before upgrading, backup your current installation including all configuration files and database
  4. 4. Download the latest stable release (1.4.6 or higher) from the official source
  5. 5. Replace the vulnerable dashboard files with the new version, preserving your configuration
  6. 6. Test the application functionality after upgrade to ensure everything works correctly
Caveat Minor release - review changelog for any configuration changes; backup before upgrading

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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