CVE-2024-1269VulnerabilityPublished 7 Feb 2024Updated 10 Jun 2025

CVE-2024-1269: SourceCodester Product Management System · Cross Site Scripting

Affects SourceCodester Product Management SystemSource CVE Database V5

Not known to be exploited · CVSS 2.4 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

2.4Low

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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 Feb 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
SourceCodester Product Management System	Affected =1.0	Fixed in–

AI-suggested

Specific mitigations include: 1) Implement strict input validation and output encoding on supplier_name and supplier_contact parameters to neutralize any injected scripts. 2) Employ Content Security Policy (CSP) headers to restrict script execution sources and reduce the impact of XSS attacks. 3) Restrict access to the /supplier.php page to only trusted users and monitor for unusual activities or input patterns. 4) Educate privileged users about the risks of clicking on suspicious links or interacting with untrusted content to reduce the chance of successful user interaction exploitation. 5) If possible, upgrade to a newer, patched version of the product once available or apply custom patches to sanitize inputs. 6) Use Web Application Firewalls (WAFs) with rules targeting XSS payloads on the affected parameters. 7) Conduct regular security assessments and code reviews focused on input handling in the product management system.

Description

A vulnerability has been found in SourceCodester Product Management System 1.0 and classified as problematic. This vulnerability affects unknown code of the file /supplier.php. The manipulation of the argument supplier_name/supplier_contact leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-253012.

Impact

For European organizations using SourceCodester Product Management System 1.0, this XSS vulnerability could lead to limited integrity impacts such as unauthorized script execution in the context of authenticated users with high privileges. Although the CVSS score is low and confidentiality and availability impacts are not present, the integrity compromise could allow attackers to perform actions on behalf of privileged users, potentially modifying supplier data or manipulating the system's behavior. The requirement for high privileges and user interaction reduces the likelihood of widespread exploitation. However, organizations with critical supplier management workflows relying on this system might face operational disruptions or data manipulation risks. Additionally, if attackers combine this vulnerability with social engineering, they could escalate the impact. Given the lack of patches, organizations must be cautious and consider compensating controls.

Summary

CVE-2024-1269 is a Cross-Site Scripting (XSS) vulnerability identified in SourceCodester Product Management System version 1.0. The vulnerability exists in the /supplier.php file, specifically through improper handling and sanitization of the input parameters supplier_name and supplier_contact. An attacker can remotely manipulate these parameters to inject malicious scripts into the web application. When a victim user accesses the affected page, the injected script executes in their browser context, potentially leading to session hijacking, defacement, or redirection to malicious sites. The vulnerability is classified under CWE-79, which covers improper neutralization of input during web page generation. The CVSS v3.1 base score is 2.4, indicating a low severity level. The vector string (AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N) shows that the attack is network exploitable with low attack complexity but requires high privileges and user interaction. No known exploits are currently reported in the wild, and no patches have been published yet. The vulnerability disclosure date is February 7, 2024.

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 11 Jul 2025, 21:49 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats