CVE-2026-5823
SQL Injection in itsourcecode CMS /borrowed_tool_report.php Allows Remote Exploitation
Publication date: 2026-04-09
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 |
|---|---|---|
| itsourcecode | construction_management_system | From 5.0.12 (inc) |
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?
This vulnerability is a SQL Injection issue found in the Construction Management System version 1.0, specifically in the file /borrowed_tool_report.php through the 'start' POST parameter.
The problem occurs because the application does not properly sanitize or validate the 'start' input before using it in SQL queries, allowing an authenticated attacker to inject malicious SQL code.
Exploitation requires valid user authentication and can be performed remotely.
Attackers can use this flaw to manipulate SQL queries, potentially gaining unauthorized access to the database, leaking sensitive data, tampering with data, taking full control of the system, or disrupting services.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data tampering, and full system compromise.
- Unauthorized database access
- Leakage of sensitive information
- Data manipulation or corruption
- Potential full control over the affected system
- Service disruption affecting business continuity
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL Injection vulnerability can be detected by testing the 'start' POST parameter in the /borrowed_tool_report.php file for injection flaws.
One common approach is to use automated tools like sqlmap to test for SQL injection by targeting the vulnerable parameter.
- Example sqlmap command: sqlmap -u "http://targetsite/borrowed_tool_report.php" --data="start=1" --risk=3 --level=5 --dbms=MySQL
- Use error-based payloads such as those involving the GTID_SUBSET function to trigger SQL errors.
- Use time-based payloads such as those involving the SLEEP function to infer database responses.
Testing requires valid user authentication since exploitation needs authenticated access.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection.
Enforce strict input validation and filtering to ensure inputs conform to expected formats.
Minimize database user permissions by avoiding the use of high-privilege accounts 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)?:
This SQL injection vulnerability allows authenticated attackers to gain unauthorized access to the database, potentially leading to sensitive data leakage, data tampering, and full system control. Such unauthorized access and data breaches can result in non-compliance with common standards and regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information.
Failure to properly secure the application against this vulnerability could lead to violations of data protection requirements, resulting in legal and financial consequences under these regulations.