CVE-2026-7073
SQL Injection in itsourcecode CMS /execute.php Enables Remote Exploit
Publication date: 2026-04-27
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-7073 is a critical SQL injection vulnerability found in the Construction Management System version 1.0, specifically in the /execute.php file. The vulnerability occurs because the application does not properly sanitize or validate the 'code' parameter received via POST requests.
Attackers can inject malicious SQL code through this parameter, which allows them to manipulate SQL queries executed by the system. This can be done remotely and does not require authentication or prior system access.
A proof-of-concept demonstrates a time-based blind SQL injection attack that causes delays in database responses, confirming the vulnerability.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, tampering with data, gaining full control over the system, and potential disruption of services.
Such impacts threaten system security and business continuity, making it a critical risk for organizations using the affected software.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability in the /execute.php file can be detected by testing the 'code' parameter for injection flaws.
A proof-of-concept uses a time-based blind SQL injection payload to confirm the vulnerability by causing a delay in the database response.
You can use the sqlmap tool to detect this vulnerability with the following command:
- python sqlmap.py --random-agent --batch -u "http://154.219.114.125:8818/execute.php" --data "code=1" --dbms=mysql --current-db
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 like 'root' or 'admin' for routine operations.
- Conduct regular security audits to detect and address vulnerabilities promptly.
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 gain unauthorized access to the database, potentially leading to sensitive data leakage, data tampering, and full system control.
Such unauthorized access and data breaches can result in non-compliance with common standards and regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information.
Failure to prevent this vulnerability could lead to violations of data protection requirements, risking legal penalties, reputational damage, and loss of trust.