CVE-2025-4033

7.3 HIGH

📋 TL;DR

This critical SQL injection vulnerability in PHPGurukul Nipah Virus Testing Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the searchdata parameter in patient-search-report.php. Attackers can potentially access, modify, or delete sensitive medical testing data. All deployments of version 1.0 are affected.

💻 Affected Systems

Products:
  • PHPGurukul Nipah Virus Testing Management System
Versions: 1.0
Operating Systems: All platforms running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of version 1.0 are vulnerable by default. The vulnerability exists in the core application code.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to exposure of all patient medical records, administrative credential theft, and potential ransomware deployment on the database server.

🟠

Likely Case

Data exfiltration of patient testing information and personal health data, potentially leading to privacy violations and regulatory compliance issues.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only allowing data viewing without modification.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Public exploit available on GitHub. SQL injection is straightforward to exploit with common tools like sqlmap.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://phpgurukul.com/

Restart Required: No

Instructions:

No official patch available. Consider migrating to alternative software or implementing workarounds.

🔧 Temporary Workarounds

Input Validation Filter

all

Add input validation to sanitize the searchdata parameter before processing

Modify patient-search-report.php to add: $searchdata = mysqli_real_escape_string($con, $_POST['searchdata']);

Web Application Firewall

all

Deploy WAF with SQL injection protection rules

🧯 If You Can't Patch

  • Isolate the system from internet access and restrict to internal network only
  • Implement strict network segmentation and monitor all database queries

🔍 How to Verify

Check if Vulnerable:

Test the /patient-search-report.php endpoint with SQL injection payloads like ' OR '1'='1

Check Version:

Check application version in admin panel or readme files

Verify Fix Applied:

Test with same payloads after implementing fixes - should return error or no data

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts after SQL injection attempts
  • Unexpected database schema queries

Network Indicators:

  • HTTP requests to patient-search-report.php with SQL keywords in parameters
  • Unusual outbound database connections

SIEM Query:

source="web_logs" AND uri="/patient-search-report.php" AND (param="searchdata" AND value CONTAINS "UNION" OR value CONTAINS "SELECT" OR value CONTAINS "OR '1'='1")

🔗 References

📤 Share & Export