VulnerabilityPublished 25 Mar 2026

CVE-2026-4825: 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, 06:59 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 25 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 29 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 this vulnerability, organizations should immediately review and restrict access to the /update_sales.php endpoint, implementing network-level controls such as IP whitelisting or VPN access to limit exposure. Input validation and parameter sanitization must be enforced on the 'sid' parameter to ensure only expected numeric or alphanumeric values are accepted, using prepared statements or parameterized queries to prevent SQL injection. If possible, upgrade to a patched version once available or apply vendor-provided fixes promptly. In the absence of official patches, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the 'sid' parameter. Conduct thorough code audits and penetration testing to identify and remediate similar injection points. Regularly monitor logs for suspicious database queries or unusual access patterns. Additionally, enforce the principle of least privilege on database accounts used by the application to limit the potential damage from successful injection attacks. Backup critical data frequently and ensure recovery procedures are tested to minimize downtime in case of compromise.

Description

A vulnerability was found in SourceCodester Sales and Inventory System 1.0. This affects an unknown part of the file /update_sales.php of the component HTTP GET Parameter Handler. The manipulation of the argument sid results in sql injection. The attack may be launched remotely. The exploit has been made public and could be used.

Impact

The exploitation of this SQL injection vulnerability can have significant impacts on organizations using the affected software. Attackers could gain unauthorized access to sensitive sales and inventory data, leading to data breaches that compromise customer information, financial records, and business operations. Data integrity could be undermined by unauthorized modification or deletion of records, potentially disrupting inventory management and sales reporting. Availability may also be affected if attackers execute destructive SQL commands or cause database errors, resulting in system downtime. For businesses relying on this system for critical operations, such disruptions could lead to financial losses, reputational damage, and regulatory compliance issues. The medium severity rating reflects the limited scope of impact and the requirement for some privileges (PR:L) but no user interaction. However, the remote exploitability and public exploit availability increase the urgency for mitigation. Organizations worldwide using this product, especially those with sensitive or regulated data, face risks of data compromise and operational disruption if the vulnerability is exploited.

Summary

CVE-2026-4825 identifies a SQL injection vulnerability in SourceCodester Sales and Inventory System version 1.0, specifically within the /update_sales.php script. The vulnerability arises due to improper sanitization or validation of the 'sid' HTTP GET parameter, which is used to identify sales records for updating. An attacker can craft a malicious 'sid' parameter value that alters the intended SQL query logic, enabling arbitrary SQL commands to be executed on the backend database. This type of injection can allow attackers to retrieve sensitive information, modify or delete data, or escalate privileges within the database context. The vulnerability is remotely exploitable without requiring authentication or user interaction, making it accessible to unauthenticated remote attackers. The CVSS 4.0 base score is 5.3, reflecting medium severity, with the vector indicating network attack vector, low attack complexity, no privileges or user interaction required, and limited impact on confidentiality, integrity, and availability. No official patches or fixes have been released at the time of publication, and although no active exploitation has been reported, the public availability of exploit code increases the risk of future attacks. The vulnerability affects only version 1.0 of the product, which is a sales and inventory management system commonly used by small to medium businesses to track sales transactions and inventory data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Mar 2026, 23:01 UTC

Technical details

References

Community reviews

Related threats