CVE-2024-0284VulnerabilityPublished 7 Jan 2024Updated 3 Jun 2025

CVE-2024-0284: Kashipara Food Management System · Cross Site Scripting

Affects Kashipara Food Management SystemSource CVE Database V5

Not known to be exploited · CVSS 3.5 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.5Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Kashipara Food Management System	Affected =1.0	Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should implement strict input validation and output encoding on the 'party_address' parameter to prevent injection of malicious scripts. Employing a web application firewall (WAF) with rules targeting XSS payloads can provide an additional layer of defense. Educating users about the risks of clicking on suspicious links and monitoring web server logs for unusual input patterns can help detect exploitation attempts. Furthermore, adopting Content Security Policy (CSP) headers can reduce the impact of XSS by restricting the execution of unauthorized scripts. Regular security assessments and code reviews should be conducted to identify and remediate similar vulnerabilities proactively.

Description

A vulnerability was found in Kashipara Food Management System up to 1.0. It has been rated as problematic. This issue affects some unknown processing of the file party_submit.php. The manipulation of the argument party_address leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-249839.

Impact

For European organizations using the Kashipara Food Management System, this XSS vulnerability could allow attackers to execute malicious scripts in the browsers of users interacting with the vulnerable application. Potential impacts include session hijacking, defacement, phishing attacks, or the injection of malicious content leading to further compromise. While the direct impact on confidentiality and availability is low, the integrity of user interactions and data could be affected. This can undermine trust in the system, especially in food management contexts where data accuracy and user trust are critical. Additionally, regulatory frameworks such as GDPR emphasize the protection of user data and secure processing, so exploitation of this vulnerability could lead to compliance issues if personal data is involved or if the attack leads to data manipulation. The requirement for user interaction somewhat limits the exploitability, but social engineering could be used to increase success rates.

Summary

CVE-2024-0284 is a cross-site scripting (XSS) vulnerability identified in the Kashipara Food Management System version 1.0. The vulnerability arises from improper sanitization of user input in the 'party_address' parameter processed by the file party_submit.php. An attacker can manipulate this parameter to inject malicious scripts, which are then executed in the context of the victim's browser. This type of vulnerability falls under CWE-79, which is a common web application security issue allowing attackers to execute arbitrary JavaScript code. The vulnerability is remotely exploitable and requires some level of user interaction, such as a victim visiting a crafted URL or submitting a form containing the malicious payload. The CVSS v3.1 base score is 3.5, indicating a low severity level, with the vector string AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N. This means the attack can be performed over the network with low attack complexity, requires low privileges, and user interaction is necessary. The impact is limited to integrity (modification of data or execution of scripts) with no direct confidentiality or availability impact. No patches or fixes have been disclosed yet, and there are no known exploits actively used in the wild at this time.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Jul 2025, 00:57 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats