Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-52381: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in Shoaib Rehmat ZIJ KART

0
Unknown
VulnerabilityCVE-2024-52381cvecve-2024-52381
Published: Thu Nov 14 2024 (11/14/2024, 17:33:08 UTC)
Source: CVE Database V5
Vendor/Project: Shoaib Rehmat
Product: ZIJ KART

Description

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 08:32:21 UTC

Technical Analysis

CVE-2024-52381 identifies a Remote File Inclusion (RFI) vulnerability in the PHP application ZIJ KART, developed by Shoaib Rehmat. The vulnerability stems from improper control over the filename parameter used in PHP's include or require statements, which allows an attacker to specify a remote file to be included and executed by the server. This type of vulnerability is critical because it can lead to remote code execution, allowing attackers to run arbitrary PHP code on the affected server. The affected versions include all releases up to and including version 1.1 of ZIJ KART. The vulnerability is categorized as a Local File Inclusion (LFI) in the description, but the title and nature suggest it is a Remote File Inclusion, which is more severe. No CVSS score has been assigned yet, and no public exploits are currently known. The vulnerability was published on November 14, 2024, and was reserved a few days earlier. The lack of patch links indicates that a fix may not yet be publicly available. The root cause is the failure to properly validate or restrict the input controlling the include/require filename, allowing attackers to specify external URLs or local paths that lead to code execution. This vulnerability is particularly dangerous in PHP applications that dynamically include files based on user input without adequate sanitization or validation. Attackers exploiting this flaw can execute arbitrary commands, steal sensitive data, or pivot within the network.

Potential Impact

The impact of CVE-2024-52381 is significant for organizations using the ZIJ KART application. Successful exploitation can lead to remote code execution, which compromises the confidentiality, integrity, and availability of the affected system. Attackers could gain unauthorized access to sensitive data, modify or delete files, install malware or backdoors, and potentially use the compromised server as a pivot point for further attacks within the network. This could result in data breaches, service disruptions, reputational damage, and regulatory penalties. Since ZIJ KART appears to be an e-commerce or content management platform, the risk extends to customer data and transaction integrity. The absence of known exploits in the wild reduces immediate risk but does not diminish the urgency of addressing the vulnerability, as attackers often develop exploits rapidly after disclosure. Organizations worldwide using this software or similar PHP applications with improper include controls are at risk. The vulnerability's ease of exploitation (no authentication or user interaction required) increases its threat level.

Mitigation Recommendations

To mitigate CVE-2024-52381, organizations should take the following specific actions: 1) Immediately audit all instances of ZIJ KART for the affected versions and restrict access to the application until patched. 2) Implement strict input validation and sanitization on any parameters controlling file inclusion, ensuring only allowed filenames or paths are accepted. 3) Disable the ability to include remote files by setting 'allow_url_include' to 'Off' in the PHP configuration. 4) Use whitelisting for include paths and avoid dynamic inclusion based on user input wherever possible. 5) Monitor web server and application logs for suspicious requests attempting to exploit file inclusion. 6) Once a patch or update is released by the vendor, apply it promptly. 7) Employ web application firewalls (WAFs) with rules to detect and block attempts to exploit file inclusion vulnerabilities. 8) Conduct regular security assessments and code reviews focusing on file inclusion and input handling. These measures go beyond generic advice by focusing on configuration hardening, proactive monitoring, and secure coding practices specific to PHP file inclusion vulnerabilities.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2024-11-11T06:38:47.502Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd753ee6bfc5ba1df03900

Added to database: 4/1/2026, 7:42:54 PM

Last enriched: 4/2/2026, 8:32:21 AM

Last updated: 4/4/2026, 8:23:13 AM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses