dbcve.org
Covid19 Testing Management SystemApplication · Unyasoft

CVE-2025-8988

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-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 vulnerability has been found in SourceCodester COVID 19 Testing Management System 1.0. This vulnerability affects unknown code of the file /bwdates-report-result.php. The manipulation of the argument fromdate leads to sql injection. The attack can 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 confidence

SQL injection vulnerability in SourceCodester COVID-19 Testing Management System 1.0 allows remote attackers to inject malicious SQL queries via the 'fromdate' parameter in /bwdates-report-result.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially exposing sensitive data, modifying or deleting database contents, or executing administrative operations.

MitigationImplement prepared statements/parameterized queries for all database interactions, particularly for the 'fromdate' parameter in bwdates-report-result.php. Alternatively, use a web application firewall (WAF) as an interim control while developing the permanent fix.

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
Covid19 Testing Management 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. Confirm the application version
    Locate and examine version files, headers, or about pages within the COVID-19 Testing Management System installation. Check for a 'version' file, README, or admin panel version display that identifies the installed version as 1.0.
    Affected if The installed version is 1.0 of SourceCodester/Unyasoft COVID-19 Testing Management System.
  2. Locate the vulnerable PHP file
    Search the web root directory for the file /bwdates-report-result.php or bwdates-report-result.php. This file is part of the reporting module for date-based COVID-19 test reports.
    Affected if The file bwdates-report-result.php exists in the application directory structure.
  3. Verify the 'fromdate' parameter is exposed
    Access the bwdates-report-result.php page via HTTP/HTTPS and examine if the 'fromdate' parameter is accepted as a GET or POST request parameter without requiring administrator-level authentication.
    Affected if The endpoint is accessible to untrusted users and accepts the 'fromdate' parameter without authentication or with low-privilege access.
  4. Check for input validation on the fromdate field
    Review the source code of bwdates-report-result.php to determine if the 'fromdate' parameter is passed directly to database queries without prepared statements, parameter binding, or input sanitization functions such as htmlspecialchars(), mysqli_real_escape_string(), or PDO quote().
    Affected if The code passes the 'fromdate' parameter directly into SQL queries without using prepared statements, parameter binding, or escape functions.

You are affected if your environment runs version 1.0 of SourceCodester COVID-19 Testing Management System and the bwdates-report-result.php file is accessible with the 'fromdate' parameter lacking parameterized query implementation.

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 prepared statements/parameterized queries for all database interactions, particularly for the 'fromdate' parameter in bwdates-report-result.php. Alternatively, use a web application firewall (WAF) as an interim control while developing the permanent fix.

Fix this in Covid19 Testing Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8988 — 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-8988 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