CVE-2024-0422VulnerabilityPublished 11 Jan 2024Updated 3 Jun 2025

CVE-2024-0422: CodeAstro POS and Inventory Management System · Cross Site Scripting

Affects CodeAstro POS and Inventory 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.4% chance of exploitation in 30 days – higher than 42% 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 11 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
CodeAstro POS and Inventory Management System	Affected =1.0	Fixed in–

AI-suggested

1. Immediate mitigation should focus on input validation and output encoding for the 'new_item' parameter on the /new_item endpoint to prevent script injection. 2. Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the browser context. 3. Employ HTTP-only and Secure flags on session cookies to mitigate session hijacking risks. 4. Conduct thorough code review and penetration testing on the affected component to identify and remediate similar XSS vectors. 5. Restrict access to the New Item Creation Page to trusted users and networks until a patch is available. 6. Educate users about the risks of clicking suspicious links or executing unknown scripts within the POS environment. 7. Monitor logs for unusual activity related to the /new_item endpoint to detect potential exploitation attempts. 8. Coordinate with the vendor to obtain or request a security patch and apply it promptly once available.

Description

A vulnerability was found in CodeAstro POS and Inventory Management System 1.0. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /new_item of the component New Item Creation Page. The manipulation of the argument new_item leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-250441 was assigned to this vulnerability.

Impact

For European organizations using CodeAstro POS and Inventory Management System version 1.0, this vulnerability could allow attackers to execute malicious scripts in the browsers of authenticated users interacting with the New Item Creation Page. While the direct impact is limited to integrity (e.g., manipulation of displayed content or execution of unauthorized scripts), it could facilitate phishing attacks, session hijacking, or unauthorized actions performed on behalf of legitimate users. Given that POS and inventory systems handle sensitive business operations and potentially customer data, even low-severity XSS vulnerabilities can be leveraged as part of a broader attack chain. The lack of confidentiality and availability impact reduces the immediate risk, but the potential for indirect damage through social engineering or session compromise remains. European organizations with online or intranet-accessible deployments of this system are at risk, especially if users have elevated privileges or if the system is integrated with other critical business applications.

Summary

CVE-2024-0422 is a Cross-Site Scripting (XSS) vulnerability identified in version 1.0 of the CodeAstro POS and Inventory Management System. The vulnerability exists in the /new_item endpoint of the New Item Creation Page component. Specifically, the flaw arises from improper sanitization or validation of the 'new_item' argument, which allows an attacker to inject malicious scripts. This vulnerability is exploitable remotely and requires some level of user interaction, as indicated by the CVSS vector (UI:R). The vulnerability does not require elevated privileges but does require some level of authentication (PR:L). The CVSS score of 3.5 classifies it as a low-severity issue, primarily impacting the integrity of the application without affecting confidentiality or availability. The attack could lead to the execution of arbitrary JavaScript in the context of the victim's browser, potentially enabling session hijacking, defacement, or redirection to malicious sites. However, no known exploits are currently observed in the wild, and no patches have been released yet. The vulnerability is categorized under CWE-79, which is a common web application security weakness related to improper neutralization of input leading to XSS.

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, 15:25 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats