CVE-2026-6190
Received Received - Intake
SQL Injection in itsourcecode CMS /employees.php Allows Remote Exploit

Publication date: 2026-04-13

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was found in itsourcecode Construction Management System 1.0. The impacted element is an unknown function of the file /employees.php. Performing a manipulation of the argument Name results in sql injection. The attack can be initiated remotely. The exploit has been made public and could be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-13
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-04-13
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
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 to gain unauthorized access to sensitive data, tamper with data, and potentially disrupt services. Such unauthorized access and data manipulation can lead to violations of data protection regulations like GDPR and HIPAA, which require the protection of personal and sensitive information against unauthorized access and breaches.

Failure to remediate this vulnerability could result in non-compliance with these standards due to potential data breaches, loss of data integrity, and inadequate security controls.


Can you explain this vulnerability to me?

CVE-2026-6190 is a critical SQL injection vulnerability found in the Construction Management System version 1.0, specifically in the "/employees.php" file.

The vulnerability occurs because the application does not properly sanitize or validate the 'name' parameter submitted via POST requests after user authentication.

Attackers who have valid credentials can inject malicious SQL code through this parameter, allowing unauthorized manipulation of SQL queries.

Two types of SQL injection techniques demonstrated are error-based SQL injection and time-based blind SQL injection, both enabling attackers to extract or infer sensitive data from the database.


How can this vulnerability impact me? :

This vulnerability can have severe impacts including unauthorized database access, leakage of sensitive data, and tampering with data.

Attackers may gain comprehensive control over the system and potentially cause service interruptions.

Such impacts threaten system security and business continuity, making immediate remediation critical.


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

This vulnerability can be detected by testing the 'name' parameter in the /employees.php file for SQL injection, especially after authenticating to the system.

A practical way to detect it is by using the sqlmap tool with a command similar to the following:

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

This command tests the 'name' parameter for SQL injection vulnerabilities by sending crafted POST requests and analyzing the responses.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include:

  • Implement prepared statements and parameter binding to separate SQL code from user input, preventing injection.
  • Apply strict input validation and filtering to ensure inputs conform to expected formats.
  • Minimize database user permissions to restrict the potential damage from compromised accounts.
  • Conduct regular security audits to identify and remediate 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