CVE-2025-14585
BaseFortify
Publication date: 2025-12-12
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 |
|---|---|---|
| angeljudesuarez | covid_tracking_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 in the itsourcecode COVID Tracking System 1.0, specifically in the /admin/?page=zone file. By manipulating the ID argument, an attacker can execute unauthorized SQL commands remotely, potentially compromising the database.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to remotely execute SQL injection attacks, which may lead to unauthorized access, data leakage, data modification, or disruption of the COVID Tracking System's database and functionality.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access, modification, and exposure of sensitive data through SQL injection, which can lead to breaches of confidentiality and data integrity. Such breaches may result in non-compliance with data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information. Failure to remediate this vulnerability could therefore compromise compliance with these standards. [1, 3, 4, 5]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the 'id' parameter in the /admin/?page=zone endpoint for SQL injection flaws. Common detection methods include using SQL injection testing tools like sqlmap to send crafted payloads to the vulnerable parameter. Example payloads include boolean-based blind, error-based, and time-based blind SQL injection techniques. For instance, using sqlmap with a command such as: sqlmap -u "http://target/cts/admin/?page=zone&id=1" --risk=3 --level=5 --batch --dbs can help identify the vulnerability. Manual testing can also be done by injecting payloads like: id=(SELECT (CASE WHEN (8116=8116) THEN '' ELSE (SELECT 8957 UNION SELECT 4538) END)) or time-based payloads like id=(CASE WHEN (2549=2549) THEN SLEEP(5) ELSE 2549 END) to observe response delays or errors indicating SQL injection. [4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameterized queries to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. 3) Minimize database user privileges by avoiding use of high-privilege accounts like 'root' or 'admin' for routine database operations. 4) Conduct regular security audits of code and systems to detect and remediate vulnerabilities promptly. If possible, consider replacing the affected product or applying secure coding practices to neutralize SQL injection risks. [4]