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

CVE-2026-54845

HIGH · 8.1 CVSS v3.1 Published 2026-06-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 8 weeks old

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
Unauthenticated Local File Inclusion in MDTF <= 1.3.8 versions.

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

Unauthenticated Local File Inclusion vulnerability in MDTF version 1.3.8 and below allows remote attackers to read arbitrary files on the server by manipulating file include parameters. This high-severity flaw requires no authentication, potentially exposing sensitive system files, configuration data, and credentials.

MitigationUpgrade MDTF to a patched version immediately. If immediate patching is not feasible, implement web application firewall rules to block directory traversal patterns and restrict file system access permissions.

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 if MDTF is installed
    Search for MDTF installation directories or check running web services for MDTF-specific paths. Look for common installation locations or check application mappings on the web server.
    Affected if MDTF is found running on the system
  2. Determine the installed MDTF version
    Check the application's version file, about page, or metadata within the MDTF installation directory. Compare the version number to 1.3.8.
    Affected if Installed version is 1.3.8 or lower
  3. Verify web interface accessibility
    Attempt to access the MDTF web interface without providing any authentication credentials. Check if the application allows unauthenticated access.
    Affected if The web interface is accessible without authentication
  4. Check for file inclusion functionality
    Inspect the application's request parameters, particularly those related to file loading, templating, or includes. Look for parameters that may accept file paths or names.
    Affected if File inclusion parameters are present and accessible without authentication

A user is affected if MDTF version 1.3.8 or lower is installed and its web interface with file inclusion parameters is accessible without authentication.

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 MDTF to a patched version immediately. If immediate patching is not feasible, implement web application firewall rules to block directory traversal patterns and restrict file system access permissions.

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-2026-54845 — 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-54845 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