VulnerabilityPublished 24 Mar 2026

CVE-2026-4781: SourceCodester Sales and Inventory System · SQL Injection

Affects SourceCodester Sales and Inventory SystemSource CVE Database V5

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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
SourceCodesterSales and Inventory System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-4781, organizations should first check for any vendor-issued patches or updates and apply them promptly once available. In the absence of official patches, implement strict input validation on the 'sid' parameter to ensure only expected data types and formats are accepted. Employ parameterized queries or prepared statements in the update_purchase.php script to prevent SQL injection. Restrict database user permissions to the minimum necessary, avoiding elevated privileges that could amplify the impact of an injection attack. Use web application firewalls (WAFs) with rules specifically designed to detect and block SQL injection attempts targeting the 'sid' parameter. Conduct thorough code reviews and security testing of the affected component to identify and remediate similar vulnerabilities. Monitor logs for unusual database query patterns or repeated requests to update_purchase.php with suspicious parameters. Educate developers on secure coding practices to prevent future injection flaws. Consider isolating the affected system from public networks or restricting access to trusted IP addresses until the vulnerability is resolved. Regularly back up critical data to enable recovery in case of data corruption or loss due to exploitation.

Description

A flaw has been found in SourceCodester Sales and Inventory System 1.0. The affected element is an unknown function of the file update_purchase.php of the component HTTP GET Parameter Handler. Executing a manipulation of the argument sid can lead to sql injection. The attack may be performed from remote. The exploit has been published and may be used.

Impact

The SQL injection vulnerability in SourceCodester Sales and Inventory System 1.0 can lead to unauthorized access to sensitive sales and inventory data, including customer information, purchase records, and stock levels. Attackers could manipulate or delete data, causing operational disruptions and financial losses. Data confidentiality is at risk as attackers may extract sensitive information from the database. Integrity is compromised through unauthorized data modification, potentially leading to inaccurate inventory or sales reports. Availability could be affected if attackers execute destructive queries or cause database errors, disrupting business operations. Since the attack requires no authentication and can be performed remotely, the threat surface is broad. Organizations relying on this system may face compliance violations if customer or financial data is exposed. The public availability of exploit code increases the likelihood of exploitation attempts, especially by opportunistic attackers. Small and medium enterprises using this software without robust security controls are particularly vulnerable. The lack of patches or vendor guidance exacerbates the risk, making timely mitigation critical to prevent data breaches and operational impact.

Summary

CVE-2026-4781 identifies a SQL injection vulnerability in SourceCodester Sales and Inventory System version 1.0, specifically within the update_purchase.php file's handling of the HTTP GET parameter 'sid'. The vulnerability arises from improper sanitization or validation of the 'sid' parameter, allowing an attacker to inject malicious SQL code. This injection can manipulate backend database queries, potentially leading to unauthorized data access, modification, or deletion. The attack vector is network-based (AV:N), with low attack complexity (AC:L), requiring no authentication (AT:N) or user interaction (UI:N). The vulnerability impacts confidentiality, integrity, and availability at a low level (VC:L, VI:L, VA:L). The scope remains unchanged (S:U), and no security controls mitigate the vulnerability (SC:N). The exploit has been publicly disclosed, though no active exploitation has been reported. The vulnerability affects only version 1.0 of the product, which is a sales and inventory management system commonly used by small to medium enterprises. The lack of patches or official fixes increases the urgency for organizations to implement alternative mitigations. The CVSS 4.0 base score of 5.3 reflects a medium severity, balancing the ease of exploitation with the limited impact scope. This vulnerability underscores the importance of secure coding practices, particularly input validation and use of parameterized queries in web applications handling database operations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Mar 2026, 23:45 UTC

Technical details

References

Community reviews

Related threats