VulnerabilityPublished 24 Mar 2026

CVE-2026-4780: 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

Organizations should immediately audit their use of SourceCodester Sales and Inventory System version 1.0 and identify any instances of the vulnerable update_out_standing.php script. Since no official patches are currently available, implement the following mitigations: 1) Apply strict input validation and sanitization on the 'sid' parameter to ensure only expected data types and formats are accepted. 2) Use parameterized queries or prepared statements to prevent SQL injection. 3) Deploy a web application firewall (WAF) with rules to detect and block SQL injection attempts targeting the vulnerable parameter. 4) Monitor logs for suspicious activities related to the 'sid' parameter and unusual database queries. 5) Restrict database user permissions to the minimum necessary to limit the impact of a successful injection. 6) Plan for an upgrade or patch deployment once the vendor releases an official fix. 7) Educate developers and administrators on secure coding practices to prevent similar vulnerabilities.

Description

A vulnerability was detected in SourceCodester Sales and Inventory System 1.0. Impacted is an unknown function of the file update_out_standing.php of the component HTTP GET Parameter Handler. Performing a manipulation of the argument sid results in sql injection. The attack is possible to be carried out remotely. The exploit is now public and may be used.

Impact

The SQL injection vulnerability can allow attackers to execute arbitrary SQL commands on the backend database, leading to unauthorized disclosure of sensitive business data, alteration or deletion of records, and potential disruption of inventory and sales operations. This can result in financial losses, reputational damage, and regulatory compliance issues for affected organizations. Since the attack requires no authentication and can be performed remotely, it increases the attack surface significantly. However, the impact is somewhat limited by the partial control over the database and the specific nature of the vulnerable parameter. Organizations using this system without proper mitigations are at risk of data breaches and operational interruptions. The public availability of exploit code raises the risk of automated attacks or exploitation by less skilled threat actors.

Summary

CVE-2026-4780 identifies a SQL injection vulnerability in the SourceCodester Sales and Inventory System version 1.0. The vulnerability resides in the update_out_standing.php script, where the HTTP GET parameter 'sid' is improperly sanitized or validated before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without requiring authentication or user interaction. The injection can lead to unauthorized data access, modification, or deletion, potentially compromising the database's confidentiality, integrity, and availability. The vulnerability is exploitable over the network with low attack complexity and no privileges required, increasing its risk profile. Although the CVSS score is medium (5.3), the partial impact on confidentiality, integrity, and availability reflects that the attacker’s control over the database is limited but still significant. The exploit has been publicly disclosed, increasing the likelihood of exploitation attempts. No official patches have been linked yet, so mitigation relies on secure coding practices, input validation, and possibly web application firewalls. The affected product is niche, primarily used by small to medium businesses for sales and inventory management, which may limit the scope but still poses a risk to organizations relying on this system.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats