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

CVE-2025-48160

HIGH · 8.1 CVSS v3.1 Published 2025-08-20
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 CocoBasic Caliris caliris-wp allows PHP Local File Inclusion.This issue affects Caliris: from n/a through <= 1.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

A Local File Inclusion (LFI) vulnerability exists in CocoBasic Caliris caliris-wp (versions <= 1.5) where improper control of filenames in PHP include/require statements allows attackers to include arbitrary local PHP files. This stems from insufficient input validation on parameters used in file inclusion operations, potentially enabling disclosure of sensitive files or code execution if attacker-controlled files can be placed on the server.

MitigationImplement strict input validation using a whitelist approach for allowed files, use basename() to strip directory traversal sequences, and avoid incorporating user-supplied input directly into include/require statements. Consider migrating to modern file inclusion patterns that avoid dynamic file paths entirely.

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 Caliris caliris-wp installation
    Locate the Caliris caliris-wp plugin or theme files in the WordPress installation directory (typically wp-content/themes/caliris or wp-content/plugins/caliris). Check the main PHP file for the version declaration, often in a header comment or version constant.
    Affected if The product is installed and the version is 1.5 or lower, or if the version cannot be determined and Caliris caliris-wp is present.
  2. Verify the affected version range
    Compare the installed version number against the affected range. Since no specific version data exists beyond <=1.5 being vulnerable, treat any version at or below 1.5 as affected.
    Affected if The installed version is 1.5 or lower, or the version cannot be verified.
  3. Inspect PHP include/require patterns
    Search the Caliris PHP source files for dynamic include, include_once, require, or require_once statements that incorporate request parameters (e.g., $_GET, $_POST, or $_REQUEST) without sanitization.
    Affected if Code uses include/require with user-supplied input directly in the path without validation or basename() filtering.
  4. Identify the vulnerable parameter
    Review the dynamic include/require code found in the previous step to identify which HTTP parameter is used in the file path (commonly seen in Caliris as parameters like 'page', 'file', 'template', or 'slug').
    Affected if A parameter accepted via GET or POST is used in include/require without whitelist validation.
  5. Check for signs of exploitation
    Review web server access logs (Apache/nginx) for requests to Caliris pages that include directory traversal sequences (e.g., ../../) or attempts to include sensitive local files (e.g., /etc/passwd, wp-config.php).
    Affected if Suspicious requests containing '../' or targeting system files are present in logs targeting Caliris endpoints.

You are affected if Caliris caliris-wp is installed with version 1.5 or lower, or if the version cannot be determined, and the codebase contains include/require statements that directly use user input without validation.

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

Implement strict input validation using a whitelist approach for allowed files, use basename() to strip directory traversal sequences, and avoid incorporating user-supplied input directly into include/require statements. Consider migrating to modern file inclusion patterns that avoid dynamic file paths entirely.

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-48160 — 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-48160 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