CVE-2026-5719
SQL Injection in itsourcecode CMS /borrowedtool.php Allows Remote Exploit
Publication date: 2026-04-07
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 | 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-5719 is a SQL injection vulnerability found in the Construction Management System V1.0, specifically in the /borrowedtool.php file. The flaw arises from improper sanitization and validation of the 'code' parameter, which is accessible via a GET request after user authentication. Attackers who have valid credentials can inject malicious SQL code through this parameter, allowing them to manipulate SQL queries executed by the system.
This vulnerability was confirmed using a time-based blind SQL injection technique on MySQL versions 5.0.12 and above, demonstrating that an attacker can cause delays in the database response by injecting specially crafted payloads.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, leakage of sensitive data, data tampering, full system control, and potential service disruption. These impacts pose significant risks to system security and business continuity.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability in /borrowedtool.php can be detected by testing the 'code' parameter for SQL injection flaws after user authentication.
A common detection method is using time-based blind SQL injection payloads, such as injecting a payload that causes a delay using the MySQL SLEEP function.
For example, the following payload can be appended to the 'code' parameter to test for the vulnerability: code=1' AND (SELECT 6278 FROM (SELECT(SLEEP(5)))alqj) AND 'PGmo'='PGmo
You can use tools like sqlmap to automate detection. An example command targeting the vulnerable URL is:
- sqlmap -u "http://target/borrowedtool.php?code=1" --cookie="session=your_session_cookie" --risk=3 --level=5 --technique=T --dbms=MySQL
Note that exploitation requires prior authentication, so valid session cookies or credentials are needed for testing.
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, preventing injection.
- Enforce 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.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Construction Management System allows attackers with valid credentials to access and manipulate sensitive data, which can lead to unauthorized data disclosure and tampering.
Such unauthorized access and potential data breaches can negatively impact compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and ensuring data integrity.
Failure to mitigate this vulnerability could result in violations of these standards due to compromised confidentiality, integrity, and availability of protected data.