VulnerabilityPublished 26 Mar 2026

CVE-2026-4850: code-projects Simple Laundry System · SQL Injection

Affects code-projects Simple Laundry SystemSource CVE Database V5

Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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 26 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
code-projectsSimple Laundry System	Affected =1.0	Fixed in–

CPE configurations (1)

cpe:2.3:a:code-projects:simple_laundry_system:*:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2026-4850, organizations should immediately implement input validation and sanitization for the Long-arm-shirtVol parameter and any other user-supplied inputs in the Simple Laundry System. Employing parameterized queries or prepared statements in the PHP code will prevent SQL injection by separating code from data. Network-level controls such as firewall rules should restrict access to the affected application to trusted IP addresses only. Monitoring and logging database queries can help detect suspicious activity indicative of exploitation attempts. If possible, isolate the application in a segmented network zone to limit exposure. Regular backups of the database should be maintained to enable recovery in case of data corruption. Finally, educate staff about the risks and signs of exploitation to improve incident response readiness.

Description

A security flaw has been discovered in code-projects Simple Laundry System 1.0. Affected is an unknown function of the file /checkregisitem.php of the component Parameter Handler. The manipulation of the argument Long-arm-shirtVol results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks.

Impact

The SQL injection vulnerability allows remote attackers to execute arbitrary SQL commands on the backend database, potentially leading to unauthorized access to sensitive customer or business data, data corruption, or denial of service through database manipulation. For organizations using the Simple Laundry System 1.0, this could mean exposure of personally identifiable information (PII), financial data, or operational records, which can result in reputational damage, regulatory penalties, and operational disruptions. Since the exploit requires no authentication, any exposed instance accessible over the network is at risk. The medium severity indicates that while the impact is significant, it may not lead to full system compromise or widespread disruption unless combined with other vulnerabilities. However, the public availability of an exploit increases the urgency for remediation. Small and medium businesses using this software may lack advanced security controls, increasing their vulnerability to exploitation and potential downstream impacts such as ransomware or data breaches.

Summary

CVE-2026-4850 is a SQL injection vulnerability identified in the Simple Laundry System 1.0 developed by code-projects. The vulnerability resides in the /checkregisitem.php script, specifically in the handling of the Long-arm-shirtVol parameter within the Parameter Handler component. Due to insufficient input validation or sanitization, an attacker can craft malicious input that alters the intended SQL query logic, enabling unauthorized database queries. This can lead to unauthorized data disclosure, modification, or deletion, impacting the confidentiality, integrity, and availability of the system's data. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 base score is 6.9, reflecting a medium severity level, with network attack vector, low complexity, no privileges or user interaction needed, and limited impact on confidentiality, integrity, and availability. Although no active exploitation has been reported, the public availability of an exploit increases the likelihood of attacks. The affected product is a niche laundry management system, likely deployed in small to medium enterprises managing laundry services. The lack of official patches or updates at the time of publication means users must rely on mitigations or upgrade paths when available.

References

Community reviews

Loading reviews…