dbcve.org
Covid19 Testing Management SystemApplication · Phpgurukul

CVE-2025-3973

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, was found in PHPGurukul COVID19 Testing Management System 1.0. This affects an unknown part of the file /check_availability.php. The manipulation of the argument mobnumber leads to sql injection. It is possible to initiate the attack 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

A critical SQL injection vulnerability exists in PHPGurukul COVID19 Testing Management System 1.0 within the /check_availability.php file. The mobnumber parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. The CVSS 9.8 score indicates potential for complete confidentiality, integrity, and availability compromise.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements, implement proper input validation on all user-supplied parameters, and apply the vendor patch when released. Until patched, consider disabling the affected functionality or implementing a web application firewall.

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 COVID19 Testing Management System is installed
    Locate the web application's installation directory. Look for files and folders typical of a PHP-based application, particularly any directory containing 'covid', 'covid19', or 'testing' in the path.
    Affected if The application is present on the server and accessible via web browser or file system.
  2. Identify the installed version
    Check for a version file, README, or any file within the application that displays or contains the version number. Common locations include a version.php file, about.php, or the main index file.
    Affected if The installed version is exactly 1.0.
  3. Locate the vulnerable file
    Navigate to the application root directory and search for the file check_availability.php. This file should exist in the main application directory.
    Affected if The file check_availability.php exists in the application directory.
  4. Verify the mobnumber parameter is handled by the application
    Open check_availability.php and examine the code for handling of a parameter named 'mobnumber'. Look for any PHP code that processes this parameter in the context of database queries.
    Affected if The file contains code that processes a 'mobnumber' parameter in SQL queries without visible sanitization functions.
  5. Determine if the application is network accessible
    Attempt to access the application's login page or check_availability.php via HTTP/HTTPS from an authorized location to confirm the application is running and exposed.
    Affected if The application is running and reachable over the network.

A user is affected if the COVID19 Testing Management System version 1.0 is installed, the file check_availability.php exists with the mobnumber parameter, and the application is accessible.

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

Replace dynamic SQL queries with parameterized queries/prepared statements, implement proper input validation on all user-supplied parameters, and apply the vendor patch when released. Until patched, consider disabling the affected functionality or implementing a web application firewall.

Fix this in Covid19 Testing Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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