CVE-2026-5564
SQL Injection in Simple Laundry System Parameter Handler Allows Remote Exploit
Publication date: 2026-04-05
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| code-projects | simple_laundry_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-5564 is a critical SQL injection vulnerability found in version 1.0 of the Simple Laundry System, specifically in the /searchguest.php file. The vulnerability occurs because the searchServiceId parameter is not properly validated or sanitized before being used in SQL queries.
This flaw allows attackers to inject malicious SQL code remotely without any authentication, enabling unauthorized access to the database, data leakage, data tampering, and potentially full control over the system.
Various SQL injection techniques can be used to exploit this vulnerability, including Boolean-based blind injection, error-based injection, time-based blind injection, and UNION-based injection.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, and data tampering.
Attackers can exploit this flaw to disrupt services, gain full control over the affected system, and manipulate or destroy data.
Since no authentication is required to exploit this vulnerability, it poses a significant risk to the confidentiality, integrity, and availability of the system and its data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability in the /searchguest.php file can be detected by testing the searchServiceId parameter with various SQL injection payloads.
- Boolean-based blind injection payload example: searchServiceId=-6166' OR 9556=9556#
- Error-based injection payload example using MySQL GTID_SUBSET function: searchServiceId=111' AND GTID_SUBSET(CONCAT(0x7176787871,(SELECT (ELT(2858=2858,1))),0x7170627a71),2858)--
- Time-based blind injection payload example using MySQL SLEEP function: searchServiceId=111' AND (SELECT 2859 FROM (SELECT(SLEEP(5)))hrsg)--
- UNION-based injection payload example to extract data: searchServiceId=111' UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,NULL,NULL,CONCAT(...)#
The sqlmap tool has been used to confirm testing and exploitation of this vulnerability, so running sqlmap against the target URL with the vulnerable parameter is recommended.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection.
- Apply strict input validation and filtering to ensure inputs conform to expected formats.
- Minimize database user permissions by avoiding use of high-privilege accounts such as root or admin for routine operations.
- Conduct regular security audits to detect and address vulnerabilities promptly.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in Simple Laundry System 1.0 allows unauthorized database access, data leakage, and data tampering without authentication. Such unauthorized access and potential exposure or alteration of sensitive data can lead to non-compliance with data protection regulations like GDPR and HIPAA, which require the protection of personal and sensitive information against unauthorized access and breaches.
Failure to remediate this vulnerability could result in violations of these standards due to compromised data integrity and confidentiality, potentially leading to legal and financial penalties.
Recommended remediation steps such as implementing prepared statements, strict input validation, minimizing database user permissions, and regular security audits are essential to maintain compliance with these regulations by securing data and preventing unauthorized access.