dbcve.org
Covid Tracking SystemApplication · Angeljudesuarez

CVE-2025-14667

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-14
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 security vulnerability has been detected in itsourcecode COVID Tracking System 1.0. The impacted element is an unknown function of the file /admin/?page=system_info. Such manipulation of the argument meta_value leads to sql injection. The attack may be performed from remote. The exploit has been disclosed publicly and may 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 meta_value parameter on the /admin/?page=system_info page. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially leading to unauthorized data access or complete system compromise.

MitigationImplement parameterized queries or prepared statements for all database operations involving user input. Apply input validation and output encoding. Restrict database user privileges to minimum required. Contact vendor for official patch if available.

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 COVID Tracking System installation
    Locate the web application's root directory or check running web services for 'covid' or 'tracking' in the application name or path. Look for files or directories named 'covid', 'covid-tracking-system', or similar.
    Affected if The application is installed and accessible on the server.
  2. Verify the installed version
    Check the application's source files, README, or configuration files for the version number. Look in the main directory for version indicators like 'version', '1.0', or check the page source of any public-facing page for version information.
    Affected if The installed version is 1.0.
  3. Confirm admin endpoint accessibility
    Attempt to access or probe the /admin/ path on the web server (e.g., http://target/admin/). Check for HTTP 200 or 302 responses indicating the directory exists and is accessible.
    Affected if The /admin/ directory is accessible without authentication or with valid admin credentials.
  4. Check for system_info page existence
    Probe the URL /admin/?page=system_info (e.g., http://target/admin/?page=system_info). Look for a valid HTTP response indicating the page exists and renders.
    Affected if The system_info page exists and loads in the application.
  5. Verify meta_value parameter handling
    Review the application source code files related to system_info or system configuration (search for 'system_info', 'meta_value', and SQL query patterns). Check if the meta_value parameter is used directly in SQL queries without prepared statements or sanitization functions.
    Affected if The meta_value parameter is processed in SQL queries without parameterized queries or input sanitization.

A user is affected if they have Angeljudesuarez Covid Tracking System version 1.0 installed with the /admin/?page=system_info page accessible and the meta_value parameter processed in SQL queries without proper sanitization or prepared statements.

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

Implement parameterized queries or prepared statements for all database operations involving user input. Apply input validation and output encoding. Restrict database user privileges to minimum required. Contact vendor for official patch if available.

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-14667 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-14667 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