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

CVE-2025-58955

HIGH · 8.1 CVSS v3.1 Published 2025-10-22
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 designervily Karzo karzo allows PHP Local File Inclusion.This issue affects Karzo: from n/a through < 2.6.

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

Local File Inclusion (LFI) vulnerability in designervily Karzo allows attackers to manipulate file inclusion paths via unsanitized input, potentially enabling unauthorized file read access or code execution on the server.

MitigationUpgrade to Karzo version 2.6 or later, which should contain the fix for this vulnerability.

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 Karzo installation
    Locate Karzo application files in the web root or application directory. Look for directories named 'karzo', 'designervily', or files with 'karzo' in the name.
    Affected if Karzo application files are found in the environment
  2. Determine Karzo version
    Check version file, composer.json, or application metadata. Common locations: /composer.json, /version.php, /app/Version, or within the admin dashboard under 'About' or 'System Info'.
    Affected if Version cannot be determined or is below 2.6
  3. Compare version to affected range
    Parse the identified version number and compare against the fixed version 2.6. Versions below 2.6 (e.g., 2.5.x, 2.4.x, 1.x) are in the vulnerable range.
    Affected if Installed version is 2.5.x or lower, or any version below 2.6
  4. Verify file inclusion functionality exists
    Examine application source code for file inclusion functions (include, require, include_once, require_once, file_get_contents with user input) that handle file paths without sanitization. Focus on routes or endpoints that accept file path parameters.
    Affected if Unsantized file inclusion code paths exist in the application and are accessible via web requests
  5. Check web server access logs
    Review HTTP access logs for suspicious requests targeting file inclusion endpoints, such as paths with '../' traversal sequences or system file references (e.g., /../../etc/passwd).
    Affected if Suspicious file path traversal requests are present in logs targeting Karzo endpoints

The environment is affected if Karzo version is identified as 2.5 or lower and file inclusion functionality is accessible without authentication or proper input 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Karzo version 2.6 or later, which should contain the fix for this vulnerability.

Recommended fix Moderate confidence

Karzo version 2.6 or later

  1. 1. Backup your current Karzo installation and database before proceeding with any upgrade.
  2. 2. Download Karzo version 2.6 or later from the official source (designervily or the vendor's distribution channel).
  3. 3. Replace the existing Karzo files with the new version 2.6 files, preserving your configuration and any custom assets.
  4. 4. Verify file permissions are correctly set (PHP files should not be writable by the web server user for security).
  5. 5. Test the application functionality to ensure the upgrade did not break existing features.
  6. 6. Confirm the vulnerability is remediated by verifying that file inclusion parameters are properly sanitized or restricted.
Caveat Review release notes for version 2.6 to check for any feature changes or deprecations that may affect your implementation

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 / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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