CVE-2026-5660
Received Received - Intake
SQL Injection in itsourcecode CMS Parameter Handler Enables Remote Exploit

Publication date: 2026-04-06

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was determined in itsourcecode Construction Management System 1.0. The impacted element is an unknown function of the file /borrowed_equip.php of the component Parameter Handler. This manipulation of the argument emp causes sql injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized.
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?

CVE-2026-5660 is a SQL injection vulnerability found in the Construction Management System version 1.0, specifically in the /borrowed_equip.php file within the Parameter Handler component. The vulnerability occurs due to improper sanitization and validation of the 'emp' parameter, which is submitted via POST after user authentication.

An attacker with valid credentials can inject malicious SQL code through this parameter, allowing them to manipulate SQL queries executed by the system. This can lead to unauthorized database access and other malicious activities.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The SQL injection vulnerability in the Construction Management System 1.0 allows attackers with valid credentials to manipulate SQL queries, potentially leading to unauthorized database access, sensitive data leakage, data tampering, and full system control.

Such impacts can compromise the confidentiality, integrity, and availability of sensitive data, which are core requirements in compliance standards like GDPR and HIPAA.

Failure to protect sensitive data against such vulnerabilities may result in non-compliance with these regulations, leading to legal and financial consequences.


How can this vulnerability impact me? :

The impact of this vulnerability includes unauthorized access to the database, leakage of sensitive data, tampering with data, gaining full control over the system, and potential disruption of services.

  • Unauthorized database access
  • Sensitive data leakage
  • Data tampering
  • Full system control
  • Potential service disruption

How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by testing the 'emp' parameter in the /borrowed_equip.php file for SQL injection vulnerabilities. A proof-of-concept demonstrates a time-based blind SQL injection using a payload that induces a delay via the SLEEP function.

A recommended command to test this vulnerability using the sqlmap tool is:

  • python sqlmap.py --random-agent --batch -u "http://154.219.114.125:8818/borrowed_equip.php" --data "submit=&emp=1" -p emp --dbms=mysql --current-db

This command targets the 'emp' parameter via POST data and attempts to detect SQL injection on a MySQL database.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include:

  • Use prepared statements and parameter binding to separate SQL code from user input, preventing injection.
  • Implement strict input validation and filtering to ensure inputs conform to expected formats, such as numeric patterns for IDs.
  • Minimize database user permissions by avoiding high-privilege accounts for routine operations.
  • Conduct regular security audits to detect and address vulnerabilities promptly.

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