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

CVE-2025-13567: 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

To mitigate this vulnerability, European organizations should immediately audit and restrict access to the /admin interface, ensuring it is not exposed to the public internet or is protected by strong network controls such as VPNs or IP whitelisting. Implement input validation and sanitization on the 'ID' parameter to reject malicious input. Refactor the backend code to use parameterized queries or prepared statements to eliminate SQL injection vectors. Conduct a comprehensive security review of the entire application to identify and remediate similar injection flaws. Monitor logs for suspicious database queries or access patterns indicative of exploitation attempts. If possible, upgrade to a patched version once available or apply vendor-provided fixes promptly. Employ web application firewalls (WAFs) with rules targeting SQL injection signatures as a temporary protective measure. Train development teams on secure coding practices to prevent future injection vulnerabilities. Finally, ensure that sensitive health data is encrypted at rest and in transit to reduce the impact of potential data exposure.

Description

A vulnerability was detected in itsourcecode COVID Tracking System 1.0. This affects an unknown function of the file /admin/?page=establishment. The manipulation of the argument ID results in sql injection. It is possible to launch the attack remotely. The exploit is now public and may be used.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of sensitive health data collected and managed by the COVID Tracking System. Unauthorized SQL injection attacks could lead to data breaches exposing personal health information, undermining public trust and potentially violating GDPR regulations. Integrity attacks could alter tracking data, affecting public health decisions and responses. Availability could also be impacted if attackers manipulate or delete critical data, disrupting pandemic monitoring efforts. Healthcare providers, government agencies, and public health organizations using this software are particularly vulnerable. The remote, unauthenticated nature of the exploit increases the attack surface, especially if administrative interfaces are not properly secured or segmented. The medium severity rating suggests that while the impact is notable, it may not lead to full system compromise or widespread disruption unless combined with other vulnerabilities. However, the critical nature of health data and pandemic tracking elevates the operational risk. European entities must consider the reputational, legal, and operational consequences of exploitation, including potential fines under data protection laws and loss of public confidence.

Summary

CVE-2025-13567 identifies a SQL injection vulnerability in the itsourcecode COVID Tracking System version 1.0. The flaw exists in the /admin/?page=establishment endpoint, where the 'ID' parameter is not properly sanitized, allowing attackers to inject arbitrary SQL commands. This vulnerability can be exploited remotely without authentication or user interaction, indicating a low barrier to attack. The CVSS 4.0 score of 5.3 reflects a medium severity, considering the attack vector is network-based, with low complexity and no privileges or user interaction required. The impact on confidentiality, integrity, and availability is limited but present, as attackers could read or modify data within the database, potentially exposing sensitive health information or disrupting system operations. Although no known exploits are currently active in the wild, the public disclosure of exploit code increases the likelihood of exploitation attempts. The vulnerability affects only version 1.0 of the product, and no patches have been published yet. The COVID Tracking System is likely deployed in healthcare or governmental environments to monitor pandemic-related data, making the data sensitivity and operational continuity critical. The lack of authentication requirements for exploitation heightens the risk, especially if administrative interfaces are exposed to the internet. The vulnerability underscores the importance of secure coding practices such as input validation and the use of parameterized queries to prevent injection flaws.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Nov 2025, 21:03 UTC

Technical details

References

Community reviews

Related threats