CVE-2026-5620
Received Received - Intake
SQL Injection in itsourcecode CMS Parameter Handler Enables Remote Attack

Publication date: 2026-04-06

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability has been found in itsourcecode Construction Management System 1.0. Affected is an unknown function of the file /borrowed_equip_report.php of the component Parameter Handler. The manipulation of the argument Home leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-06
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-04-06
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
itsourcecode construction_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 flaw found in the Construction Management System version 1.0, specifically in the file /borrowed_equip_report.php. It occurs because the application does not properly sanitize or validate the input parameter (noted as 'Home' in the CVE but 'start' in the resource) before using it in SQL queries. This allows an attacker to inject malicious SQL code remotely, potentially without authentication, to manipulate the database.


How can this vulnerability impact me? :

Exploiting this SQL injection vulnerability can lead to unauthorized access to the database, leakage of sensitive data, tampering with data, gaining full control over the system, and causing service disruptions. This severely compromises 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 the "/borrowed_equip_report.php" file can be detected using SQL injection testing tools such as sqlmap. The vulnerable parameter is 'start' (POST parameter).

A typical detection approach involves sending crafted payloads to the 'start' parameter to check for SQL injection flaws, including error-based and time-based blind SQL injection techniques.

For example, using sqlmap, you can run commands targeting the vulnerable parameter to confirm the presence of the vulnerability.

  • sqlmap -u "http://target/borrowed_equip_report.php" --data="start=1" --risk=3 --level=5 --dbms=mysql
  • Use error-based payloads exploiting SQL clauses like WHERE, HAVING, ORDER BY, or GROUP BY.
  • Use time-based payloads with functions like SLEEP to confirm injection.

What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input.

Strict input validation and filtering should be enforced to ensure that inputs conform to expected formats.

Minimize database user permissions to reduce the potential impact of exploitation.

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 can lead to unauthorized database access, sensitive data leakage, and data tampering. Such security breaches can result in non-compliance with common standards and regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive data.

Failure to protect against SQL injection attacks may expose personal data to unauthorized parties, violating data privacy and security requirements. This can lead to legal penalties, reputational damage, and loss of trust.

Therefore, the presence of this vulnerability directly impacts the ability of an organization using the affected system to comply with data protection regulations.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart