dbcve.org
Nipah Virus Testing Management SystemApplication · Phpgurukul

CVE-2025-1580

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-23
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 Nipah Virus Testing Management System 1.0. It has been classified as critical. Affected is an unknown function of the file /search-report-result.php. The manipulation of the argument searchdata leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The initial researcher advisory mentions contradicting parameter names to be affected.

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 Nipah Virus Testing Management System 1.0. The vulnerability is located in the /search-report-result.php file where user-supplied input via the 'searchdata' parameter is directly concatenated into SQL queries without proper sanitization or parameterized statements. This allows remote attackers to inject malicious SQL code, potentially enabling unauthorized data access, data manipulation, or complete database compromise.

MitigationReplace direct SQL query construction with prepared statements/parameterized queries to properly sanitize the searchdata parameter. Additionally, implement input validation, apply output encoding, and consider deploying a WAF as a temporary compensating control until the code fix is fully implemented.

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
Nipah Virus 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 the application is installed
    Locate the PHPGurukul Nipah Virus Testing Management System installation directory on the server. Common locations include web root directories such as /var/www/html/, /htdocs/, or C:\inetpub\wwwroot\ on Windows. Look for files matching this application name.
    Affected if The application is present on the system and the installation directory contains files from PHPGurukul Nipah Virus Testing Management System.
  2. Confirm the installed version
    Check for a version file, README, or any file containing version information within the application directory. Alternatively, view the footer or header of any PHP page for a version number display.
    Affected if The installed version is exactly 1.0, as this is the only affected version listed.
  3. Locate the vulnerable file
    Navigate to the application directory and search for the file named 'search-report-result.php'. This file should exist in the web-accessible portion of the application.
    Affected if The file search-report-result.php exists in the application directory.
  4. Examine the SQL query construction in the vulnerable file
    Open search-report-result.php in a text editor and search for occurrences of the 'searchdata' parameter. Look for SQL query strings where this parameter is concatenated directly into the query without the use of prepared statements, parameter binding, or sanitization functions.
    Affected if The 'searchdata' parameter is directly concatenated into SQL queries without sanitization, prepared statements, or parameter binding.
  5. Determine if the vulnerable code is reachable
    Verify that the search-report-result.php page is accessible via HTTP/HTTPS requests. Attempt to access the page using the application's base URL followed by /search-report-result.php.
    Affected if The page is accessible over the network and accepts user input through the searchdata parameter.

A user is affected if they have PHPGurukul Nipah Virus Testing Management System version 1.0 installed with the search-report-result.php file present and accessible, where the 'searchdata' parameter is handled with direct SQL concatenation.

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 direct SQL query construction with prepared statements/parameterized queries to properly sanitize the searchdata parameter. Additionally, implement input validation, apply output encoding, and consider deploying a WAF as a temporary compensating control until the code fix is fully implemented.

Fix this in Nipah Virus Testing Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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