CVE-2026-4579
Received Received - Intake
SQL Injection in Simple Laundry System /viewdetail.php Allows Remote Exploit

Publication date: 2026-03-23

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was identified in code-projects Simple Laundry System 1.0. This affects an unknown function of the file /viewdetail.php of the component Parameters Handler. The manipulation of the argument serviceId leads to sql injection. Remote exploitation of the attack is possible. The exploit is publicly available and might be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-23
Last Modified
2026-04-29
Generated
2026-06-16
AI Q&A
2026-03-23
EPSS Evaluated
2026-06-14
NVD
CVE-2026-4579
EUVD
EUVD-2026-14388
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
code-projects simple_laundry_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-4579 is a critical SQL injection vulnerability found in the Simple Laundry System version 1.0, specifically in the /viewdetail.php file. The issue arises because the serviceId parameter is used directly in SQL queries without proper input validation or sanitization.

This flaw allows attackers to inject malicious SQL code remotely without needing any authentication, which can lead to unauthorized access to the database, data leakage, modification, deletion, or even full system compromise.

The vulnerability has been demonstrated using various SQL injection techniques such as boolean-based blind, error-based, and time-based blind injections.

Impact Analysis

This vulnerability can have severe impacts including unauthorized access to sensitive data stored in the database, data leakage, and unauthorized modification or deletion of data.

Attackers can exploit this remotely without authentication, potentially leading to full system compromise or disruption of services.

  • Data leakage exposing sensitive customer or business information.
  • Data modification or deletion causing loss of integrity and availability.
  • Full system compromise if attackers leverage the vulnerability to execute further attacks.
  • Service disruption impacting business continuity.
Compliance Impact

I don't know

Detection Guidance

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by testing the `serviceId` parameter in the `/viewdetail.php` file for SQL injection flaws. Using tools like sqlmap can automate detection and confirm the vulnerability.'}, {'type': 'list_item', 'content': 'Use sqlmap with a command such as: sqlmap -u "http://target/viewdetail.php?serviceId=1" --batch --dbs'}, {'type': 'list_item', 'content': 'Manually test with payloads like boolean-based blind injection: serviceId=(SELECT (CASE WHEN (1281=1281) THEN 4 ELSE (SELECT 7797 UNION SELECT 6323) END))'}, {'type': 'list_item', 'content': 'Test error-based injection (MySQL >= 5.6): serviceId=4 AND GTID_SUBSET(CONCAT(0x716a6b6b71,(SELECT (ELT(2003=2003,1))),0x717a717071),2003)'}, {'type': 'list_item', 'content': 'Test time-based blind injection (MySQL >= 5.0.12): serviceId=4 AND (SELECT 9040 FROM (SELECT(SLEEP(5)))Qrrj)'}] [1]

Mitigation Strategies

Immediate mitigation steps include:

  • Implement prepared statements with parameter binding to separate SQL code from user input.
  • Apply strict input validation and filtering to ensure parameters conform to expected formats.
  • Minimize database user permissions by avoiding use of high-privilege accounts for application database connections.
  • Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly.
Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-4579. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart