CVE-2026-5565
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-5565 is a critical SQL injection vulnerability found in version 1.0 of the Simple Laundry System, specifically in the /delmemberinfo.php file. The issue arises because the userid parameter is used directly in SQL queries without proper input validation or sanitization.
This allows attackers to inject malicious SQL code remotely without any authentication or authorization, potentially manipulating the database in unauthorized ways.
- Vulnerable Parameter: userid (GET request)
- Vulnerability Type: SQL Injection (including boolean-based blind, error-based, time-based blind, and UNION query types)
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, data leakage, data modification or deletion, and potentially full system compromise.
Attackers can exploit this flaw to disrupt service availability, threaten system security, and compromise business continuity.
- Leak sensitive data
- Modify or delete data
- Gain full system control
- Cause service interruptions
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the `userid` parameter in the `/delmemberinfo.php` file for SQL injection flaws. Various types of SQL injection techniques such as boolean-based blind, error-based, time-based blind, and UNION query injections can be used to confirm the presence of the vulnerability.
- Use automated tools like sqlmap to test the `userid` parameter for SQL injection.
- Example sqlmap command: sqlmap -u "http://target/delmemberinfo.php?userid=1" --batch --dbs
- Manual payloads to test include:
- - Boolean-based blind: userid=(SELECT (CASE WHEN (7027=7027) THEN 15 ELSE (SELECT 4369 UNION SELECT 2605) END))
- - Error-based (MySQL >= 5.6): userid=15 AND GTID_SUBSET(CONCAT(0x717a717871,(SELECT (ELT(7593=7593,1))),0x71626a6a71),7593)
- - Time-based blind (MySQL >= 5.0.12): userid=15 AND (SELECT 1400 FROM (SELECT(SLEEP(5)))cvFV)
- - UNION query (12 columns): userid=-5273 UNION ALL SELECT CONCAT(0x717a717871,0x4a4a456c54615450685654467966555586e56444a777a5a4e6b73616274465661754575694f5a,0x71626a6a71),NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL-- -
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Use prepared statements with parameter binding to separate SQL code from user input, preventing injection.
- Implement strict input validation and filtering to ensure that inputs conform to expected formats.
- Minimize database user permissions by avoiding the use of high-privilege accounts such as root or admin for routine database operations.
- Conduct regular security audits of the code and systems to identify and remediate 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 attackers to perform unauthorized database access, leak sensitive data, modify or delete data, and gain full system control. Such impacts can lead to violations of data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and breaches.
Failure to remediate this vulnerability could result in non-compliance with these standards due to potential data breaches, unauthorized data manipulation, and lack of adequate security controls.
Mitigations such as using prepared statements, input validation, minimizing database permissions, and regular security audits are essential to maintain compliance with these regulations.