Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13568: SQL Injection in itsourcecode COVID Tracking System

0
Medium
VulnerabilityCVE-2025-13568cvecve-2025-13568
Published: Sun Nov 23 2025 (11/23/2025, 20:32:06 UTC)
Source: CVE Database V5
Vendor/Project: itsourcecode
Product: COVID Tracking System

Description

A flaw has been found in itsourcecode COVID Tracking System 1.0. This impacts an unknown function of the file /admin/?page=people. This manipulation of the argument ID causes sql injection. The attack can be initiated remotely. The exploit has been published and may be used.

AI-Powered Analysis

AILast updated: 11/23/2025, 21:02:42 UTC

Technical Analysis

CVE-2025-13568 identifies a SQL injection vulnerability in the itsourcecode COVID Tracking System version 1.0. The vulnerability exists in an unspecified function within the /admin/?page=people endpoint, where the ID parameter is improperly sanitized, allowing an attacker to inject malicious SQL commands. This flaw can be exploited remotely without requiring user interaction, but does require low-level privileges, such as an authenticated user with limited rights. The vulnerability impacts the confidentiality, integrity, and availability of the system's database by enabling unauthorized data retrieval, modification, or deletion. The CVSS 4.0 score of 5.3 reflects a medium severity, considering the attack vector is network-based, with low attack complexity and no user interaction needed, but requiring some privileges. No patches have been published yet, and no active exploits are reported in the wild, though proof-of-concept exploit code is available, increasing the risk of exploitation. The COVID Tracking System likely stores sensitive health data, making this vulnerability particularly concerning for organizations managing pandemic response data. The lack of authentication bypass means attackers must have some access, but the low privilege requirement means many users could potentially exploit this flaw. The vulnerability highlights the need for secure coding practices around input validation and parameterized queries in web applications handling sensitive data.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of sensitive COVID-19 tracking data, which may include personal health information of citizens. Exploitation could lead to unauthorized data disclosure, manipulation of health records, or disruption of tracking operations, undermining public health efforts and trust. The availability of the system could also be affected if attackers execute destructive SQL commands. Given the critical role of COVID tracking systems in managing public health responses, any compromise could have cascading effects on healthcare services and policy decisions. Moreover, data breaches involving health information are subject to strict regulatory penalties under GDPR, increasing the legal and financial impact on affected organizations. The medium severity rating suggests that while the vulnerability is not trivially exploitable by unauthenticated attackers, the risk remains substantial due to the sensitivity of the data and the availability of exploit code.

Mitigation Recommendations

Organizations should immediately audit and sanitize all inputs to the /admin/?page=people endpoint, specifically the ID parameter, by implementing parameterized queries or prepared statements to prevent SQL injection. Restrict administrative interface access using strong authentication and network segmentation to limit exposure. Monitor database logs and application behavior for unusual queries or access patterns indicative of exploitation attempts. Apply the principle of least privilege to user accounts, ensuring that users have only the necessary permissions to perform their roles. If possible, isolate the COVID Tracking System from external networks or place it behind a web application firewall (WAF) configured to detect and block SQL injection attempts. Since no official patch is currently available, consider temporary mitigations such as disabling the vulnerable functionality or restricting access to trusted IP addresses. Regularly update and review security controls and prepare to deploy patches once released by the vendor. Conduct security awareness training for administrators to recognize and respond to potential exploitation signs.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-11-22T19:03:20.427Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 692372e6962646bb5af86ebd

Added to database: 11/23/2025, 8:47:34 PM

Last enriched: 11/23/2025, 9:02:42 PM

Last updated: 11/25/2025, 1:56:40 AM

Views: 15

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats