CVE-2025-13585
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 was detected in itsourcecode COVID Tracking System 1.0. This issue affects some unknown processing of the file /login.php. The manipulation of the argument code results in sql injection. The attack may be performed from remote. The exploit is now 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 confidenceA SQL injection vulnerability exists in itsourcecode COVID Tracking System 1.0's login.php file. The 'code' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL statements. The critical CVSS score of 9.8 indicates complete compromise potential including data exfiltration or authentication bypass.
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 a directory containing 'login.php' and 'covid' or 'tracking' in the path, or check for files with 'covid' in the name.Affected if The application files are found on the server
-
Verify the exact version numberCheck the application's source code, README, or any version file for the version string. Compare against '1.0'.Affected if The installed version is exactly 1.0 (Angeljudesuarez Covid Tracking System)
-
Examine login.php for the vulnerable code parameterOpen /login.php and search for usage of the 'code' parameter in SQL queries. Look for unsanitized concatenation of $_POST['code'] or $_GET['code'] directly into SQL statements.Affected if The 'code' parameter is used in a SQL query without parameterized queries or input sanitization
-
Confirm the SQL injection vulnerability existsIf 'code' is found in a dynamic SQL query, verify it is not wrapped in prepared statements, mysqli_prepare, PDO::prepare, or escaped with mysqli_real_escape_string.Affected if The SQL query uses direct string concatenation with the 'code' parameter without protection
-
Check if the application is exposed to remote usersDetermine if login.php is accessible over the network via HTTP/HTTPS to unauthenticated users.Affected if The login.php endpoint is publicly accessible or accessible to untrusted users
A defender is affected if the Angeljudesuarez Covid Tracking System version 1.0 is installed with login.php accessible and the 'code' parameter used in a dynamic (unparameterized) SQL query.
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 dataremediate by implementing parameterized queries/prepared statements for all SQL queries involving user input, particularly the 'code' parameter in login.php, and conducting comprehensive input validation. Given the public exploit and critical severity, immediate patching is critical.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13585 — 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-13585 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