CVE-2026-5150
SQL Injection in Accounting System 1.0 Parameter Handler (Remote
Publication date: 2026-03-30
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 | 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-5150 is an SQL injection vulnerability found in the Accounting System Project version 1.0, specifically in the file /viewin_costumer.php. The issue occurs because the cos_id parameter is used directly in SQL queries without proper input validation or sanitization.
This allows attackers to inject malicious SQL code remotely without needing any authentication, enabling them to manipulate SQL queries.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control, and potential service disruption.
Attackers can use 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 sensitive data.
Because the attack can be launched remotely and does not require user authentication, the risk and impact are significant.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The CVE-2026-5150 vulnerability can be detected by testing the vulnerable parameter cos_id in the /viewin_costumer.php file for SQL injection flaws.
- Boolean-based blind injection test using payload: cos_id=-3206' OR 3895=3895#
- Error-based injection test for MySQL ≥ 5.0 using payload: cos_id=1' OR (SELECT 5241 FROM(SELECT COUNT(*),CONCAT(0x717a7a6b71,(SELECT (ELT(5241=5241,1))),0x7178787671,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- QcJz
- Time-based blind injection test using SLEEP function: cos_id=1' AND (SELECT 1906 FROM (SELECT(SLEEP(5)))TsKc)-- jqSb
- UNION-based injection test to extract data: cos_id=1' UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,CONCAT(0x717a7a6b71,0x5146784f6c707076536255724b71514c436b585447665252504b594f55667463786578644d4f4e52,0x7178787671),NULL#
Additionally, the vulnerability was confirmed using the sqlmap tool targeting the URL parameter injection, which can be used as a detection method.
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.
- Implement strict input validation and filtering to ensure inputs conform to expected formats.
- Minimize database user permissions by avoiding high-privilege accounts for routine operations.
- Conduct regular security audits to detect and remediate vulnerabilities promptly.
These steps are critical to protect system security and data integrity from exploitation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Accounting System 1.0 allows attackers to gain unauthorized database access, leading to data leakage, data tampering, and potential full system control. Such unauthorized access and data compromise can result in violations of data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information.
Failure to remediate this vulnerability promptly could lead to non-compliance with these standards due to inadequate protection of data confidentiality, integrity, and availability.
Recommended mitigations such as using prepared statements, strict input validation, minimizing database privileges, and regular security audits are essential to maintain compliance with these regulations.