CVE-2026-5033
SQL Injection in code-projects Accounting System Parameter Handler
Publication date: 2026-03-29
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 |
|---|---|---|
| sherlock | accounting_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-5033 is a critical SQL injection vulnerability found in the Accounting System Project version 1.0, specifically in the file /view_costumer.php. The issue arises because the cos_id parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication.
The vulnerability enables various SQL injection techniques such as Boolean-based blind injection, error-based injection, time-based blind injection, and UNION-based injection to extract or manipulate database data.
Exploitation can lead to unauthorized database access, data leakage, data modification or deletion, and potentially full system compromise or service disruption.
How can this vulnerability impact me? :
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 flaw remotely without any authentication, potentially leading to full system compromise or disruption of services.
Such impacts can result in loss of business continuity, damage to reputation, and financial losses.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability can be detected by testing the affected parameter cos_id in the /view_costumer.php file for SQL injection flaws.
Several SQL injection techniques can be used to detect the vulnerability, including Boolean-based blind injection, error-based injection, time-based blind injection, and UNION-based injection.
Example payloads to test the cos_id parameter include:
- Boolean-based blind injection using MySQL RLIKE operator: cos_id=1' RLIKE (SELECT (CASE WHEN (8811=8811) THEN 1 ELSE 0x28 END))--
- Error-based injection exploiting MySQL >= 5.0: cos_id=1' OR (SELECT 9186 FROM(SELECT COUNT(*),CONCAT(0x717a6a6271,(SELECT (ELT(9186=9186,1))),0x716b717871,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)--
- Time-based blind injection using MySQL SLEEP function: cos_id=1' AND (SELECT 8262 FROM (SELECT(SLEEP(5)))vRpr)--
- UNION-based injection to extract data: cos_id=1' UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,NULL,CONCAT(0x717a6a6271,0x4b6a56545a43497770717a6f6e615472724c6961706a6e6b63584147776d706d4a6e7941544e5168,0x716b717871)#
Testing can also be performed using automated tools such as sqlmap to confirm the presence of the vulnerability and enumerate the database.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Implement prepared statements with parameter binding to separate SQL code from user input.
- Enforce strict input validation and filtering to ensure parameters conform to expected formats.
- Minimize database user privileges by avoiding the use of high-privilege accounts such as root or admin for application database connections.
- Conduct regular security audits of code and systems 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 the Accounting System Project 1.0 allows unauthorized database access, data leakage, and data modification or deletion. Such unauthorized access and potential exposure of sensitive data can lead to non-compliance with 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 violations of these standards due to compromised confidentiality, integrity, and availability of protected data, potentially leading to legal penalties, reputational damage, and loss of trust.