dbcve.org
Covid19 Testing Management SystemApplication · Phpgurukul

CVE-2025-3972

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-27
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
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, which was classified as critical, has been found in PHPGurukul COVID19 Testing Management System 1.0. Affected by this issue is some unknown functionality of the file /bwdates-report-result.php. The manipulation of the argument todate leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.

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 COVID19 Testing Management System 1.0 allows remote attackers to inject malicious SQL queries via the 'todate' parameter in /bwdates-report-result.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially exfiltrating sensitive data, modifying records, or achieving code execution. Other parameters may also be vulnerable.

MitigationImmediate remediation requires implementing prepared statements/parameterized queries for all database interactions in the affected file and throughout the application. Until a patch is applied, network-level filtering should restrict access to the vulnerable endpoint.

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 the COVID19 Testing Management System installation and identify its version number. Check any version file, about page, or admin dashboard for the installed version. Common locations include a /version file, footer of pages, or within the admin panel.
    Affected if The installed version is 1.0 of Phpgurukul Covid19 Testing Management System
  2. Locate the vulnerable PHP file
    Search for the file bwdates-report-result.php in the web root directory. This file handles date range reporting functionality and contains the vulnerable SQL query handler.
    Affected if The file /bwdates-report-result.php exists in the web application directory
  3. Inspect the vulnerable code in bwdates-report-result.php
    Open bwdates-report-result.php in a text editor and search for SQL queries that use the 'todate' parameter. Look for direct insertion of $_POST or $_GET['todate'] into SQL statements without prepared statements, parameter binding, or input sanitization.
    Affected if The code contains unsanitized 'todate' parameter usage in SQL queries without prepared statements or parameter binding
  4. Verify other parameters may be vulnerable
    Review all $_POST and $_GET parameter usage in bwdates-report-result.php. Check if any other parameters like 'fromdate' are used in SQL queries without proper input validation or parameterized queries.
    Affected if Additional parameters (such as 'fromdate') are used in SQL queries without sanitization or prepared statements
  5. Check web server accessibility of the endpoint
    Verify that the /bwdates-report-result.php endpoint is accessible via HTTP/HTTPS from the web server. This endpoint typically processes date range reports and accepts user input through POST or GET parameters.
    Affected if The vulnerable endpoint is accessible and accepts user input without protection

A user is affected if they are running Phpgurukul Covid19 Testing Management System version 1.0 and the bwdates-report-result.php file with unsanitized SQL parameters is accessible on their server.

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

Immediate remediation requires implementing prepared statements/parameterized queries for all database interactions in the affected file and throughout the application. Until a patch is applied, network-level filtering should restrict access to the vulnerable endpoint.

Fix this in Covid19 Testing Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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