CVE-2025-13585VulnerabilityPublished 24 Nov 2025Updated 7 Dec 2025

CVE-2025-13585: 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 36% 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 24 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

Organizations should immediately audit their deployment of the itsourcecode COVID Tracking System version 1.0 and restrict access to the /login.php endpoint where feasible. Implement strict input validation and sanitization on the 'code' parameter, employing parameterized queries or prepared statements to prevent SQL injection. If available, apply official patches or updates from the vendor promptly. In the absence of patches, consider deploying web application firewalls (WAFs) with rules to detect and block SQL injection attempts targeting the vulnerable parameter. Conduct thorough code reviews and penetration testing to identify and remediate similar injection flaws elsewhere in the application. Monitor logs for suspicious activity indicative of exploitation attempts. Additionally, ensure that database accounts used by the application have the least privileges necessary to limit potential damage. Finally, establish incident response plans to quickly address any breaches stemming from this vulnerability.

Description

A vulnerability was detected in itsourcecode COVID Tracking System 1.0. This issue affects some unknown processing of the file /login.php. The manipulation of the argument code results in sql injection. The attack may be performed from remote. The exploit is now public and may be used.

Impact

For European organizations, exploitation of this SQL injection vulnerability could result in unauthorized access to sensitive health data collected by the COVID Tracking System, including personally identifiable information and health status. This could lead to privacy violations, regulatory penalties under GDPR, and reputational damage. Data integrity could be compromised, affecting the accuracy of tracking and reporting COVID-19 cases, which is critical for public health decision-making. Availability impacts may arise if attackers disrupt the system or delete data, impeding pandemic response efforts. Given the public health importance, such disruptions could have broader societal consequences. The medium severity rating indicates a significant but not critical risk, yet the public availability of exploit code elevates urgency. European healthcare providers, government agencies, and contractors using this system are particularly vulnerable, especially if they have not applied mitigations or patches.

Summary

CVE-2025-13585 identifies a SQL injection vulnerability in the itsourcecode COVID Tracking System version 1.0, located in the /login.php script where the 'code' parameter is improperly sanitized. This allows attackers to inject arbitrary SQL commands remotely without authentication or user interaction. The vulnerability has a CVSS 4.0 base score of 6.9 (medium severity), reflecting network attack vector, low attack complexity, and no privileges or user interaction required. Exploiting this flaw could enable attackers to extract sensitive data, modify or delete records, or disrupt service availability by manipulating the backend database. The vulnerability arises from inadequate input validation and lack of parameterized queries in the login processing logic. Although no active exploits are reported, the public disclosure of exploit code increases the likelihood of attacks. The COVID Tracking System is critical for public health monitoring, making the integrity and confidentiality of its data paramount. The vulnerability's exploitation could lead to exposure of personal health information, undermining trust and compliance with data protection regulations such as GDPR.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Dec 2025, 07:17 UTC

Technical details

References

Community reviews

Related threats