Covid Tracking SystemApplication · Angeljudesuarez

CVE-2025-14585

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in itsourcecode COVID Tracking System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/?page=zone. The manipulation of the argument ID results in sql injection. The attack may be launched remotely. The exploit has been made public and could be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in itsourcecode COVID Tracking System 1.0 allows remote attackers to inject malicious SQL queries through the ID parameter at /admin/?page=zone. The CVSS 9.8 indicates critical severity, likely enabling unauthorized database access or potential command execution depending on database configuration.

MitigationRemediate by replacing dynamic SQL queries with parameterized queries/prepared statements for the ID parameter in the zone functionality. If no vendor patch is available, restrict network access to the admin panel or deploy a WAF as a temporary control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Covid Tracking SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if COVID Tracking System is deployed
    Locate web application files or running services matching the Angeljudesuarez COVID Tracking System. Check web server document roots for directories containing COVID-related tracking scripts or check running web services on common ports (80, 443, 8080).
    Affected if The application is present and matches the COVID Tracking System name/vendor.
  2. Verify installed version is 1.0
    Inspect application files for version indicators such as version.txt, README files, or version strings in source code comments. Compare against the affected version range (= 1.0).
    Affected if The installed version is exactly 1.0.
  3. Confirm admin panel is accessible
    Attempt to access or verify the presence of the /admin/ endpoint in the web application. This is typically found at the path /admin/ relative to the application root.
    Affected if The /admin/ panel is reachable over the network.
  4. Check if zone functionality is enabled
    Verify the /admin/?page=zone endpoint exists and is accessible. This requires the zone module to be present in the application's page routing.
    Affected if The zone page (page=zone) is accessible and responds to requests.
  5. Confirm ID parameter accepts input
    Inspect the zone page functionality to verify the ID parameter is processed by the application. This parameter is where the SQL injection occurs.
    Affected if The ID parameter at /admin/?page=zone accepts user-supplied values without parameterized query handling.

A user is affected if they have Angeljudesuarez Covid Tracking System version 1.0 deployed with the /admin/?page=zone endpoint accessible and the ID parameter handling user input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remediate by replacing dynamic SQL queries with parameterized queries/prepared statements for the ID parameter in the zone functionality. If no vendor patch is available, restrict network access to the admin panel or deploy a WAF as a temporary control.

Fix this in Covid Tracking System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14585 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14585 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data