CVE-2025-14585VulnerabilityPublished 12 Dec 2025Updated 15 Dec 2025

CVE-2025-14585: itsourcecode COVID Tracking System · SQL Injection

Affects itsourcecode COVID Tracking SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
itsourcecode COVID Tracking System	Affected =1.0	Fixed in–

AI-suggested

Organizations should immediately audit their deployment of the itsourcecode COVID Tracking System version 1.0 and apply patches or updates if available. In the absence of official patches, implement input validation and sanitization on the ID parameter in the /admin/?page=zone endpoint to prevent SQL injection. Refactor the code to use parameterized queries or prepared statements to eliminate direct concatenation of user input into SQL commands. Restrict access to the admin interface by IP whitelisting, VPNs, or multi-factor authentication to reduce exposure. Conduct regular security assessments and penetration testing focused on injection flaws. Monitor logs for unusual database queries or access patterns indicative of exploitation attempts. Educate administrators on the risks and signs of SQL injection attacks. Finally, consider migrating to more secure and actively maintained COVID tracking solutions if feasible.

Description

A vulnerability was found in itsourcecode COVID Tracking System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/?page=zone. The manipulation of the argument ID results in sql injection. The attack may be launched remotely. The exploit has been made public and could be used.

Impact

For European organizations, exploitation of this vulnerability could lead to unauthorized access to sensitive COVID-19 tracking data, including personal health information, which is subject to strict GDPR regulations. Data breaches could result in legal penalties, loss of public trust, and operational disruptions in pandemic response efforts. Integrity violations could lead to falsified data, undermining public health decisions and reporting accuracy. Availability impacts, while low, could disrupt administrative functions of the tracking system. Given the critical nature of health data and the importance of accurate COVID tracking, the threat poses a significant risk to healthcare providers, government health agencies, and any organizations relying on this system. The medium severity rating suggests a moderate but non-negligible risk, especially if combined with other vulnerabilities or insider threats.

Summary

CVE-2025-14585 is a SQL injection vulnerability identified in the itsourcecode COVID Tracking System version 1.0. The flaw exists in the /admin/?page=zone endpoint, where the ID parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This vulnerability can be exploited remotely without authentication or user interaction, making it highly accessible to attackers. The injection could lead to unauthorized reading, modification, or deletion of database records, potentially exposing sensitive health data or disrupting system operations. The CVSS 4.0 score of 6.9 reflects a medium severity, considering the ease of exploitation (no privileges or user interaction required) and the limited scope of impact (confidentiality, integrity, and availability are impacted to a low extent). Although no known exploits are currently active in the wild, the public availability of exploit code increases the likelihood of future attacks. The vulnerability highlights the importance of secure coding practices, particularly input validation and the use of parameterized queries in web applications handling sensitive data. The COVID Tracking System is critical for pandemic management, so exploitation could have broader public health implications.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Dec 2025, 22:53 UTC

Technical details

References

Community reviews

Related threats