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-13567: SQL Injection in itsourcecode COVID Tracking System

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

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.

AI-Powered Analysis

AILast updated: 11/23/2025, 20:13:16 UTC

Technical Analysis

CVE-2025-13567 is a SQL injection vulnerability identified in the itsourcecode COVID Tracking System version 1.0. The vulnerability exists in the /admin/?page=establishment endpoint, where the ID parameter is improperly sanitized, allowing attackers to inject malicious SQL commands. This flaw can be exploited remotely without requiring user interaction or elevated privileges, although some level of low privilege (PR:L) is needed, possibly meaning a logged-in user with limited rights. The injection can lead to unauthorized reading, modification, or deletion of sensitive data stored in the backend database, impacting confidentiality, integrity, and availability. The CVSS 4.0 score of 5.3 reflects a medium severity, considering the ease of exploitation (low complexity, no user interaction), but limited scope and impact due to the requirement of some privileges and limited confidentiality/integrity/availability impact. No patches or official fixes have been published yet, and while no active exploits are reported in the wild, the public availability of exploit code increases the risk of attacks. The vulnerability highlights the critical need for secure coding practices such as input validation and the use of parameterized queries in web applications, especially those handling sensitive public health data during a pandemic. The affected system is likely used by public health authorities or organizations tracking COVID-19 data, making it a valuable target for attackers seeking to disrupt health data integrity or steal sensitive information.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of COVID-19 tracking data, which may include sensitive personal health information. Exploitation could lead to unauthorized data disclosure, manipulation of health records, or disruption of tracking services, undermining public health efforts and trust. Given the critical nature of pandemic response data, any compromise could have cascading effects on health policy decisions and resource allocation. Additionally, data breaches involving health information are subject to strict regulatory penalties under GDPR, increasing legal and financial risks. The availability impact is moderate but could affect administrative functions critical for managing establishments in the tracking system. Organizations relying on this software without timely mitigation may face reputational damage and operational disruptions. The remote exploitability and public availability of exploit code increase the likelihood of attacks, especially from opportunistic or targeted threat actors aiming to exploit pandemic-related systems.

Mitigation Recommendations

1. Immediately implement input validation and sanitization on all parameters, especially the ID parameter in the /admin/?page=establishment endpoint. 2. Refactor the backend code to use parameterized queries or prepared statements to prevent SQL injection. 3. Restrict access to the administration interface using network segmentation, VPNs, or IP whitelisting to limit exposure. 4. Enforce the principle of least privilege for user accounts accessing the system, ensuring minimal rights are granted. 5. Monitor logs for unusual database queries or access patterns indicative of injection attempts. 6. If patches become available from itsourcecode, apply them promptly. 7. Conduct a thorough security audit of the entire application to identify and remediate other potential injection points. 8. Educate administrators and developers on secure coding practices and the importance of timely vulnerability management. 9. Consider deploying Web Application Firewalls (WAFs) with rules tailored to detect and block SQL injection attempts targeting this system. 10. Backup critical data regularly and ensure recovery procedures are tested to mitigate potential data loss from exploitation.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 69236ac46d4acfe6c0ac2364

Added to database: 11/23/2025, 8:12:52 PM

Last enriched: 11/23/2025, 8:13:16 PM

Last updated: 11/25/2025, 1:57:33 AM

Views: 19

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