CVE-2026-4571VulnerabilityPublished 23 Mar 2026

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

Affects SourceCodester Sales and Inventory SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% 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 23 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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

1. Apply vendor patches or updates as soon as they become available to address the vulnerability directly. 2. In the absence of official patches, implement web application firewall (WAF) rules to detect and block SQL injection attempts targeting the 'searchtxt' parameter. 3. Conduct input validation and sanitization on all user-supplied data, especially POST parameters, to ensure only expected input is processed. 4. Employ parameterized queries or prepared statements in the application code to prevent SQL injection. 5. Restrict database user privileges to the minimum necessary to limit the impact of a potential injection attack. 6. Monitor logs for suspicious activities related to the /view_payments.php endpoint and unusual database queries. 7. Consider network segmentation and limiting external access to the affected system to reduce exposure. 8. Educate development and security teams about secure coding practices to prevent similar vulnerabilities in future releases.

Description

A security flaw has been discovered in SourceCodester Sales and Inventory System 1.0. Affected by this vulnerability is an unknown functionality of the file /view_payments.php of the component HTTP POST Request Handler. Performing a manipulation of the argument searchtxt results in sql injection. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks.

Impact

The SQL Injection vulnerability can lead to unauthorized access to sensitive financial and inventory data, potentially exposing customer information, payment records, and business-critical data. Attackers could manipulate or delete records, causing data integrity issues and operational disruptions. In worst cases, attackers might escalate their access to execute arbitrary commands on the database server, leading to full system compromise. This can result in financial losses, reputational damage, regulatory penalties, and operational downtime. Since the vulnerability is remotely exploitable without authentication, it poses a significant risk to organizations using the affected software, especially those with internet-facing deployments. The public release of exploit code increases the likelihood of attacks, including automated scanning and exploitation by opportunistic threat actors.

Summary

CVE-2026-4571 is a SQL Injection vulnerability identified in SourceCodester Sales and Inventory System version 1.0. The vulnerability arises from improper sanitization of the 'searchtxt' parameter in the /view_payments.php component, which handles HTTP POST requests. By manipulating this parameter, an attacker can inject malicious SQL code into the backend database queries. This injection can lead to unauthorized data disclosure, data modification, or even full compromise of the database depending on the privileges of the database user. The attack vector is remote and does not require authentication or user interaction, making it easier to exploit. The CVSS 4.0 base score is 5.3 (medium), reflecting the moderate impact and ease of exploitation. The vulnerability affects confidentiality, integrity, and availability but with limited scope and no privilege escalation or scope change. Although no patches have been linked yet, the public availability of exploit code increases the urgency for mitigation. Organizations relying on this system for sales and inventory management should assess their exposure and apply necessary controls to prevent exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats