VulnerabilityPublished 9 Mar 2026Updated 10 Mar 2026

CVE-2026-3793: 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 32% 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 9 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

Organizations should implement strict input validation and sanitization on all GET parameters, especially 'sellid', to prevent injection of malicious SQL code. Employing parameterized queries or prepared statements in the sales_invoice1.php file is critical to eliminate direct concatenation of user input into SQL commands. Restricting access to the vulnerable endpoint via network controls such as firewalls or VPNs can reduce exposure. Monitoring and logging database queries for unusual activity may help detect exploitation attempts early. If possible, upgrade to a patched version once available or consider alternative inventory management solutions with secure coding practices. Conduct regular security assessments and code reviews to identify similar vulnerabilities. Educate developers on secure coding standards to prevent future injection flaws. Finally, maintain backups of critical data to enable recovery in case of data corruption or loss.

Description

A vulnerability was determined in SourceCodester Sales and Inventory System 1.0. This vulnerability affects unknown code of the file sales_invoice1.php of the component GET Parameter Handler. This manipulation of the argument sellid causes sql injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized.

Impact

The SQL injection vulnerability allows remote attackers to manipulate database queries, potentially leading to unauthorized access to sensitive sales and inventory data. This can result in data breaches exposing customer information, financial records, or inventory details. Attackers might also alter or delete critical data, disrupting business operations and causing financial losses. The integrity of sales records could be compromised, affecting reporting and decision-making. Availability may be impacted if attackers execute destructive queries or cause database errors. Given the vulnerability requires only low privileges and no user interaction, exploitation can be automated and widespread once exploit code is available. Organizations relying on this system may face regulatory compliance issues and reputational damage if exploited. The lack of patches increases the window of exposure, emphasizing the need for immediate mitigation.

Summary

CVE-2026-3793 identifies a SQL injection vulnerability in SourceCodester Sales and Inventory System version 1.0, specifically within the sales_invoice1.php file that handles the GET parameter 'sellid'. The vulnerability arises from improper sanitization or validation of this parameter, allowing an attacker to inject malicious SQL code remotely without requiring authentication or user interaction. Exploiting this flaw can enable attackers to perform unauthorized database queries, potentially leading to data leakage, modification, or deletion. The vulnerability affects the confidentiality, integrity, and availability of the system's data. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L, indicating low privileges), no user interaction (UI:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). Despite the moderate CVSS score of 5.3, the public disclosure of the exploit code increases the risk of exploitation. No official patches have been linked yet, so organizations must rely on mitigations such as input validation and query parameterization. The vulnerability is limited to version 1.0 of the product, which may still be in use in small to medium enterprises relying on SourceCodester's inventory solutions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Mar 2026, 09:26 UTC

Technical details

References

Community reviews

Related threats