VulnerabilityPublished 8 Mar 2026Updated 11 Mar 2026

CVE-2026-3753: 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 24% 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 8 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

Immediately implement input validation and sanitization on all user-supplied parameters, especially the sid parameter in /add_sales_print.php.
Refactor the application code to use parameterized queries or prepared statements to prevent SQL injection.
Restrict database user permissions to the minimum necessary, avoiding elevated privileges that could exacerbate the impact of an injection attack.
Monitor logs for suspicious SQL query patterns or unexpected database errors indicative of exploitation attempts.
If possible, isolate the affected system behind a firewall or VPN to limit exposure to untrusted networks.
Conduct a thorough code review of the entire application to identify and remediate other potential injection points.
Engage with the vendor or community to obtain patches or updates addressing this vulnerability.
Educate developers and administrators on secure coding practices and the importance of input validation.
Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block injection attempts targeting this parameter.
Regularly back up databases and test restoration procedures to minimize damage from potential data corruption.

Description

A vulnerability has been found in SourceCodester Sales and Inventory System up to 1.0. The impacted element is an unknown function of the file /add_sales_print.php. Such manipulation of the argument sid leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Impact

The SQL injection vulnerability can lead to unauthorized access to sensitive business data, including sales records and inventory details, potentially resulting in data breaches and loss of business confidentiality. Attackers might modify or delete critical data, impacting data integrity and disrupting business operations. Although the impact on availability is limited, crafted queries could cause database errors or service interruptions. The remote and unauthenticated nature of the exploit increases the attack surface, allowing attackers to target vulnerable systems over the internet. Organizations relying on this system may face financial losses, reputational damage, and regulatory compliance issues if exploited. The medium severity rating reflects the moderate but tangible risk posed by this vulnerability, especially in environments lacking compensating controls.

Summary

CVE-2026-3753 identifies a SQL injection vulnerability in the SourceCodester Sales and Inventory System version 1.0, affecting the /add_sales_print.php script through the sid parameter. This vulnerability arises from improper sanitization or validation of user-supplied input, allowing an attacker to inject malicious SQL code remotely without requiring authentication or user interaction. The injection flaw can be exploited to manipulate backend database queries, potentially exposing sensitive sales and inventory data, altering records, or causing denial of service by corrupting database operations. The CVSS 4.0 vector indicates a network attack vector with low complexity and no privileges or user interaction needed, but with limited impact on confidentiality, integrity, and availability. Although no active exploitation has been observed, the public disclosure of the exploit code increases the risk of opportunistic attacks. The vulnerability is confined to version 1.0 of the product, which is a niche sales and inventory management system commonly used by small to medium enterprises. The lack of available patches or official fixes necessitates immediate mitigation through secure coding practices and environment hardening.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats