dbcve.org
Covid19 Testing Management SystemApplication · Phpgurukul

CVE-2025-3976

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 was found in PHPGurukul COVID19 Testing Management System 1.0. It has been classified as critical. Affected is an unknown function of the file /new-user-testing.php. The manipulation of the argument mobilenumber leads to sql injection. It is possible to launch 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

SQL injection vulnerability in PHPGurukul COVID19 Testing Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the mobilenumber parameter in /new-user-testing.php. The application fails to properly sanitize user input before using it in database queries, enabling attackers to manipulate query logic, extract sensitive data, or potentially execute system commands depending on database configuration.

MitigationImplement prepared statements/parameterized queries for all database operations in new-user-testing.php and related files. Apply input validation and output encoding. Monitor the vendor for official patches.

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. Identify if PHPGurukul COVID19 Testing Management System is installed
    Search the web server document root for files named 'new-user-testing.php' or look for application directories containing 'covid' or 'covid19' in the path. Common locations include /var/www/html, /www/html, or C:\inetpub\wwwroot.
    Affected if The application directory and the file new-user-testing.php exist on the server.
  2. Confirm the installed version is 1.0
    Check for a version file, readme.txt, or CHANGELOG in the application root directory. Alternatively, view the source of any PHP file in the application for a version comment or constant.
    Affected if The application version is exactly 1.0 as stated in the affected versions.
  3. Verify the vulnerable file exists and processes the mobilenumber parameter
    Open new-user-testing.php in a text editor or use 'grep' to search for 'mobilenumber' within the file. Look for SQL queries that use this parameter without prepared statements.
    Affected if The file exists and contains database queries using the mobilenumber parameter directly.
  4. Check if user input reaches the vulnerable code path
    Review the new-user-testing.php file to determine if the mobilenumber field is received via POST or GET and passed directly to database queries without sanitization functions like htmlspecialchars, mysqli_real_escape_string, or parameterized queries.
    Affected if The mobilenumber parameter is used in SQL queries without proper escaping or prepared statements.
  5. Confirm the application database is accessible
    Check if the application database configuration file (often config.php, db.php, or similar) is present and points to a live database. Verify network accessibility if the database is remote.
    Affected if The application is connected to an accessible database and the vulnerable code is reachable over the network.

You are affected if PHPGurukul COVID19 Testing Management System version 1.0 is installed, the file new-user-testing.php exists, and it processes the mobilenumber parameter in SQL queries without prepared statements.

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 operations in new-user-testing.php and related files. Apply input validation and output encoding. Monitor the vendor for official patches.

Fix this in Covid19 Testing Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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