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

CVE-2025-69342

HIGH · 7.5 CVSS v3.1 Published 2026-01-06
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 VanKarWai Calafate calafate allows PHP Local File Inclusion.This issue affects Calafate: from n/a through <= 1.7.7.

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 VanKarWai Calafate PHP application allows remote attackers to read arbitrary files on the server via improper control of filename parameters in include/require statements.

MitigationImplement strict input validation and whitelist-based file inclusion logic; disable allow_url_include in PHP configuration; review and patch file inclusion routines to prevent path traversal.

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 VanKarWai Calafate installation
    Search for files containing 'Calafate' or 'VanKarWai' in the web root directory. Common locations include /var/www/html, /www, or C:\inetpub\wwwroot. Look for directories named 'calafate', 'vankarwai', or similar variations.
    Affected if The application is present on the server and contains include/require statements using dynamic filename parameters.
  2. Determine the installed version
    Locate any version file, README, or changelog within the Calafate application directory. Check composer.json, package.json, or any configuration file that displays the software version. Compare against any publicly disclosed affected version range.
    Affected if The installed version falls within the affected range (if known) or is an unpatched version of the application.
  3. Inspect file inclusion code
    Review PHP files that contain include, include_once, require, or require_once statements. Search for dynamic usage such as include($_GET['page']) or require($filename) where the filename parameter originates from user input without sanitization.
    Affected if Dynamic file inclusion using unsanitized user-supplied input (GET, POST, COOKIE parameters) is present in the codebase.
  4. Verify PHP configuration settings
    Locate the php.ini configuration file (run 'php -i' or check /etc/php/*/php.ini). Inspect the following directives: allow_url_include should be Off (if available), and open_basedir restrictions should be configured appropriately.
    Affected if allow_url_include is enabled (set to On) or no open_basedir restrictions exist, increasing exploitability.
  5. Check for path traversal patterns in access logs
    Review web server access logs (Apache access_log, Nginx access.log) for requests containing '../' sequences or absolute file paths (e.g., /etc/passwd, ../../Windows/win.ini) targeting Calafate application endpoints.
    Affected if Suspicious path traversal requests are found in logs targeting the vulnerable file inclusion parameters.

The server is affected if VanKarWai Calafate is installed with dynamic file inclusion routines using unsanitized user input, particularly when PHP allow_url_include is enabled or when access logs show exploitation attempts.

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 input validation and whitelist-based file inclusion logic; disable allow_url_include in PHP configuration; review and patch file inclusion routines to prevent path traversal.

Recommended fix Moderate confidence

Calafate version > 1.7.7 (latest stable release)

  1. 1. Identify all instances of VanKarWai Calafate in your environment
  2. 2. Check the currently installed version of Calafate (typically found in a version file, config, or footer of the application)
  3. 3. Obtain the latest stable release of Calafate from the official vendor source
  4. 4. Before deploying the upgrade, perform a full backup of the application files and database
  5. 5. Test the upgrade in a staging environment to verify compatibility
  6. 6. Deploy the upgraded version to production
  7. 7. Validate that the file inclusion vulnerability is no longer present by reviewing the code paths that handle include/require statements
Caveat Review release notes for any breaking changes between 1.7.7 and the target upgrade version

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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