CVE-2025-14584
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 · uneditedA vulnerability has been found in itsourcecode COVID Tracking System 1.0. Affected is an unknown function of the file /admin/login.php of the component Admin Login. The manipulation of the argument Username leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public 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 confidenceSQL injection vulnerability in itsourcecode COVID Tracking System 1.0's admin login page (/admin/login.php). The 'Username' parameter is not properly sanitized, allowing attackers to inject malicious SQL queries. This is a critical remote code execution vector given the admin panel access.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the COVID Tracking System installationSearch the web server document root for directories containing 'covid', 'tracking', or 'covid19' in the name. Common paths include /var/www/html/, /www/, or C:\inetpub\wwwroot\Affected if The application is installed on the server
-
Verify the application versionCheck for a version file (version.php, README, or CHANGELOG) in the installation directory, or examine meta information in the main index or login page sourceAffected if The installed version is 1.0 (Angeljudesuarez Covid Tracking System 1.0)
-
Confirm admin login page existsCheck for the presence of /admin/login.php relative to the installation root directoryAffected if The file /admin/login.php exists in the application
-
Inspect the login code for SQL injection vulnerabilityOpen /admin/login.php and examine the SQL query handling the Username parameter. Look for direct string concatenation or unsanitized $_POST['username'] usage in SQL queries without prepared statements or escaping functions like mysqli_real_escape_stringAffected if The code uses direct parameter insertion in SQL queries (e.g., "SELECT * FROM users WHERE username='" . $_POST['username'] . "'") without parameterized queries or proper escaping
-
Determine if admin panel is network accessibleAttempt to access the /admin/login.php endpoint from a browser or curl request. Verify if the login page loads and responds to unauthenticated requestsAffected if The admin login page is reachable over the network (internal or external)
You are affected if the COVID Tracking System version 1.0 is installed, the /admin/login.php file exists, and the Username parameter in the login code is handled without parameterized queries or proper input sanitization.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries with parameterized queries (prepared statements) for the username (and password) parameters. Implement input validation and enable WAF rules as an interim control.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14584 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14584 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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