CVE-2026-6191
SQL Injection in itsourcecode CMS /equipments.php Allows Remote Exploit
Publication date: 2026-04-13
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?
This vulnerability is a SQL injection issue found in the Construction Management System version 1.0, specifically in the /equipments.php file. It occurs because the application does not properly sanitize or validate the 'name' input parameter before using it in SQL queries. This allows an authenticated attacker to inject malicious SQL code remotely.
The vulnerability enables attackers to manipulate the database queries, potentially leading to unauthorized access or modification of data.
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 to perform unauthorized database access, leak sensitive data, tamper with data, and gain system control. Such impacts can lead to violations of data protection requirements under common standards and regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information from unauthorized access and breaches.
Failure to remediate this vulnerability could result in non-compliance due to potential data breaches, unauthorized data manipulation, and service interruptions, all of which are critical concerns under these regulations.
Recommended remediation steps such as using prepared statements, input validation, minimizing database permissions, and regular security audits help mitigate these risks and support compliance efforts.
How can this vulnerability impact me? :
Exploiting this SQL injection vulnerability can have severe impacts, including unauthorized access to the database, leakage of sensitive information, tampering with data, gaining full control over the system, and causing service interruptions. These consequences threaten both 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 Construction Management System 1.0 can be detected by testing the 'name' parameter in the /equipments.php file for injection flaws.
A practical detection method is to use the sqlmap tool to test the parameter for SQL injection.
- Example sqlmap command: python sqlmap.py --random-agent --batch -u "http://<target-ip>:<port>/equipments.php" --data "submit=&name=1" -p name --dbms=mysql --current-db
This command tests the 'name' POST parameter for SQL injection vulnerabilities against a MySQL database.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this SQL injection vulnerability, the following immediate steps are recommended:
- 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 the use of high-privilege accounts like 'root' or 'admin' for routine database operations.
- Conduct regular security audits of the code and systems to identify and address vulnerabilities promptly.