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

CVE-2025-58995

HIGH · 8.1 CVSS v3.1 Published 2025-11-06
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 Creatives_Planet Leblix leblix allows PHP Local File Inclusion.This issue affects Leblix: from n/a through <= 2.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

This is a PHP Local File Inclusion (LFI) vulnerability in the Leblix application (version <= 2.4). The vulnerability stems from improper control of filenames in PHP include/require statements, allowing attackers to manipulate file path parameters to include arbitrary files from the server filesystem, potentially leading to remote code execution.

MitigationImplement strict input validation on all file inclusion parameters, preferably using a whitelist approach or storing allowed file references as keys in an array rather than directly using user input in include/require statements.

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 Leblix installation version
    Check the application's version file, composer.json, or admin panel for the installed version number. Common locations include a VERSION file in the root directory, version defined in composer.json, or displayed in the admin backend.
    Affected if The installed version is 2.4 or any version lower than 2.4.
  2. Locate PHP file inclusion statements
    Search the application source code for PHP include, require, include_once, or require_once statements. Use grep or similar tools to find patterns like 'include($_GET' or 'require($' across all PHP files in the application.
    Affected if The application uses include/require statements where the file path is derived from user-supplied input such as GET/POST parameters.
  3. Identify user-controlled parameters in inclusion calls
    Examine the file inclusion statements found in step 2. Trace the source of the path variable to determine if it comes directly or indirectly from user input ($_GET, $_POST, $_REQUEST, or URL parameters).
    Affected if The file path parameter in any include/require statement can be controlled or influenced by external user input without proper sanitization.
  4. Check for input validation on file inclusion parameters
    Review the code handling file inclusion parameters. Look for validation logic such as whitelist checks, array key lookups, or path sanitization before the include/require statement is executed.
    Affected if No strict input validation, allowlist, or safe mapping array is used to restrict which files can be included.
  5. Test for directory traversal capability
    If file inclusion with user input exists, attempt to verify if the application allows path traversal sequences like '../' in the parameter value to access files outside the intended directory.
    Affected if The application permits directory traversal characters in file inclusion parameters, allowing arbitrary file access from the server filesystem.

You are affected if Leblix version 2.4 or lower is installed AND the application contains PHP include/require statements using user-controlled input without strict validation or allowlisting.

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 on all file inclusion parameters, preferably using a whitelist approach or storing allowed file references as keys in an array rather than directly using user input in include/require statements.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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