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

CVE-2024-52381

HIGH · 8.1 CVSS v3.1 Published 2024-11-14
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 Shoaib Rehmat ZIJ KART zij-kart allows PHP Local File Inclusion.This issue affects ZIJ KART: from n/a through <= 1.1.

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 ZIJ KART application where user-supplied input is improperly used in PHP include/require statements without adequate validation. An attacker could manipulate file path parameters to include arbitrary local PHP files, potentially leading to sensitive file disclosure or remote code execution.

MitigationImplement strict input validation using basename() or realpath() functions, whitelist allowed file paths, and ensure include statements use hardcoded base paths rather than direct user input.

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 ZIJ KART installation
    Search the web root directory for files containing 'ZIJ KART', 'zijkart', or common PHP files like index.php, config.php that reference the application name. Use: find /var/www -type f -name '*.php' -exec grep -l -i 'zijkart' {} \;
    Affected if The ZIJ KART application is present on the server
  2. Locate PHP include/require statements with dynamic input
    Review PHP source files in the application directory for include, include_once, require, or require_once statements that use variables, request parameters, or user input without sanitization. Search patterns like: include($_GET[...]), require($file), include_once("$path" . $_REQUEST[...])
    Affected if Dynamic file inclusion using unsanitized user input is found in the codebase
  3. Identify vulnerable file path parameters
    Examine PHP files that handle file operations (file inclusion, file reading) and trace how parameters like 'file', 'path', 'page', 'include', 'template', or 'action' are processed. Check if these parameters flow directly into include/require statements
    Affected if URL parameters control the file path in include/require statements without validation
  4. Verify lack of input validation functions
    Search the identified vulnerable files for security functions like basename(), realpath(), pathinfo(), or whitelist validation. Check if the application uses a fixed base directory for includes: grep -E 'basename|realpath|pathinfo' *.php
    Affected if No basename(), realpath(), or whitelist validation is present before file inclusion
  5. Test file inclusion capability
    If you have access to a test environment, attempt a benign LFI test: access a known file like /etc/passwd through the suspected parameter (e.g., index.php?file=../../../etc/passwd) to confirm the vulnerability exists
    Affected if The application returns content from arbitrary local files via the parameter

A user is affected if the ZIJ KART application is installed and contains PHP code where user-supplied parameters are used directly in include/require statements without basename(), realpath(), or whitelist 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 basename() or realpath() functions, whitelist allowed file paths, and ensure include statements use hardcoded base paths rather than direct user input.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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