CVE-2025-13569VulnerabilityPublished 23 Nov 2025Updated 24 Nov 2025

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

Affects itsourcecode COVID Tracking SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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 23 Nov 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

1. Immediately restrict access to the /admin interface using network-level controls such as VPNs, IP whitelisting, or firewall rules to limit exposure. 2. Implement strict input validation and sanitization on the 'ID' parameter to reject malicious payloads. 3. Refactor database queries to use parameterized statements or prepared queries to eliminate SQL injection vectors. 4. Monitor logs for suspicious query patterns or repeated access attempts to the vulnerable endpoint. 5. If patches become available from itsourcecode, apply them promptly. 6. Conduct a thorough security review of the entire COVID Tracking System codebase to identify and remediate similar injection flaws. 7. Educate administrators on secure configuration and the risks of exposing administrative interfaces publicly. 8. Consider deploying Web Application Firewalls (WAFs) with SQL injection detection rules as an interim protective measure. 9. Regularly back up databases to enable recovery in case of data corruption or deletion. 10. Coordinate with national cybersecurity agencies for threat intelligence sharing and incident response support.

Description

A vulnerability has been found in itsourcecode COVID Tracking System 1.0. Affected is an unknown function of the file /admin/?page=city. Such manipulation of the argument ID leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations, this vulnerability poses a risk of unauthorized access to sensitive COVID-19 tracking data, which could lead to privacy violations, manipulation of public health information, and disruption of pandemic monitoring efforts. Healthcare providers and government agencies relying on the affected software may experience data breaches exposing personal health information or operational data, potentially undermining public trust and compliance with GDPR. Integrity attacks could result in falsified COVID case data, impacting decision-making and resource allocation. Availability could also be affected if attackers use the vulnerability to delete or corrupt database records, causing service outages. The medium severity rating reflects moderate impact, but the critical nature of health data and pandemic response elevates the operational risk. European entities must consider the reputational and regulatory consequences of exploitation, especially given the public health implications.

Summary

CVE-2025-13569 identifies a SQL injection vulnerability in the itsourcecode COVID Tracking System version 1.0, specifically within the /admin/?page=city endpoint where the 'ID' parameter is improperly sanitized. This flaw allows remote attackers to inject arbitrary SQL commands without requiring authentication or user interaction, exploiting the system over the network. The vulnerability can lead to unauthorized reading, modification, or deletion of database records, impacting confidentiality, integrity, and availability of critical COVID tracking data. The CVSS 4.0 vector indicates no privileges or user interaction are needed, with low complexity of attack and limited scope confined to the vulnerable component. Although no exploits have been observed in the wild, the public disclosure increases the likelihood of exploitation attempts. The COVID Tracking System is likely deployed in healthcare and governmental environments managing pandemic data, making it a sensitive target. The lack of available patches necessitates immediate mitigation through input validation, use of prepared statements, and restricting administrative interface access. The vulnerability underscores the importance of secure coding practices in public health software, where data integrity and availability are crucial for pandemic response.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Nov 2025, 22:08 UTC

Technical details

References

Community reviews

Related threats