CVE-2025-67285
SQL Injection in ITSourcecode COVID Tracking System Admin Page
Publication date: 2025-12-17
Last updated on: 2025-12-17
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| itsourcecode | covid_tracking_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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection found in the '/cts/admin/?page=zone' file of the ITSourcecode COVID Tracking System v1.0. It occurs because the 'id' parameter is used directly in SQL queries without proper validation or sanitization, allowing attackers to inject malicious SQL code. This can lead to unauthorized database access and manipulation. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow attackers to access, modify, or delete data in the database without authorization. They may gain full control over the system, cause data leakage, and disrupt services. The attack does not require user authentication, making it easier to exploit. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the '/cts/admin/?page=zone' endpoint for SQL injection using the 'id' parameter. Example payloads to test include boolean-based blind: 'id=1 AND 2013=2013', error-based (MySQL ≥ 5.0): 'id=1 AND (SELECT 3741 FROM(SELECT COUNT(*),CONCAT(0x717a7a7171,(SELECT (ELT(3741=3741,1))),0x71786b7071,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)', and time-based blind (MySQL ≥ 5.0.12): 'id=1 AND (SELECT 1294 FROM (SELECT(SLEEP(5)))TKZM)'. Additionally, the sqlmap tool can be used to confirm the vulnerability by sending POST requests to '/cts/classes/Zone.php?f=save' with parameters including 'id', 'code', 'name', and 'description'. [1]
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 to ensure data conforms to expected formats, minimizing database user permissions by avoiding the use of high-privilege accounts (such as root or admin) for routine operations, and conducting regular security audits to detect and address vulnerabilities promptly. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized database access, data leakage, data modification or deletion, and full system control without authentication. Such unauthorized access and potential data breaches can lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data. Failure to secure the system against this SQL injection vulnerability risks violating data protection requirements and could result in regulatory penalties. [1]