CVE-2026-6007
SQL Injection in itsourcecode CMS /del.php Allows Remote Exploit
Publication date: 2026-04-10
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
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 can lead to unauthorized database access, sensitive data leakage, data tampering, and full system control by attackers. Such impacts can compromise the confidentiality, integrity, and availability of sensitive data.
These consequences may result in non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data against unauthorized access and breaches.
Therefore, exploitation of this vulnerability could lead to violations of data protection requirements, potentially resulting in legal and regulatory penalties.
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 /del.php file through the 'equipname' parameter.
The application does not properly sanitize or validate the 'equipname' input before using it in SQL queries, allowing an attacker with valid credentials to inject malicious SQL code.
This can be exploited remotely by authenticated users to manipulate database queries.
Proof-of-concept attacks include Boolean-based blind injection, error-based injection, and time-based blind injection techniques against a MySQL database.
How can this vulnerability impact me? :
Exploitation of this SQL injection vulnerability can lead to unauthorized access to the database, leakage of sensitive data, data tampering, full system control by the attacker, and disruption of services.
This severely compromises system security and can impact business continuity.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability in the /del.php file can be detected by testing the 'equipname' POST parameter for SQL injection flaws. Proof-of-concept payloads include Boolean-based blind injection using RLIKE conditions, error-based injection leveraging GTID_SUBSET functions, and time-based blind injection employing the SLEEP function.
To detect the vulnerability, you can use tools like sqlmap or manual curl commands to send crafted POST requests to /del.php with payloads designed to trigger SQL injection responses.
- Example curl command to test time-based blind SQL injection: curl -X POST -d "equipname=1' OR IF(SLEEP(5),1,0)-- -" http://target/del.php
- Use sqlmap with: sqlmap -u "http://target/del.php" --data="equipname=test" --technique=BEUST --level=5 --risk=3
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, enforcing strict input validation and filtering on the 'equipname' parameter, and minimizing database user permissions by avoiding high-privilege accounts for routine operations.
Additionally, conduct regular security audits to detect and remediate vulnerabilities promptly. Since no fixes were indicated for version 1.0 at the time of reporting, these mitigations are critical to reduce risk.