CVE-2025-5614

6.3 MEDIUM

📋 TL;DR

This critical SQL injection vulnerability in PHPGurukul Online Fire Reporting System 1.2 allows attackers to manipulate database queries through the 'serachdata' parameter in /search-report-result.php. Remote attackers can potentially access, modify, or delete sensitive data in the database. Organizations using this specific version of the fire reporting system are affected.

💻 Affected Systems

Products:
  • PHPGurukul Online Fire Reporting System
Versions: 1.2
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in default installation. Requires PHP environment with database backend.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, or full system takeover via SQL injection to execute arbitrary commands.

🟠

Likely Case

Unauthorized access to sensitive fire reporting data, potential extraction of user credentials, and manipulation of fire incident records.

🟢

If Mitigated

Limited impact with proper input validation, parameterized queries, and database permission restrictions in place.

🌐 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 via search parameter requires minimal technical skill.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://phpgurukul.com/

Restart Required: No

Instructions:

No official patch available. Check vendor website for updates. Consider implementing input validation and parameterized queries manually.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to sanitize searchdata parameter before processing

Modify /search-report-result.php to include: $searchdata = mysqli_real_escape_string($con, $_POST['serachdata']);

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns

Add WAF rule: Detect and block SQL injection patterns in POST parameters

🧯 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 from the application

🔍 How to Verify

Check if Vulnerable:

Test /search-report-result.php with SQL injection payloads in serachdata parameter: ' OR '1'='1

Check Version:

Check application files or documentation for version 1.2 indication

Verify Fix Applied:

Test with same payloads after implementing fixes - should return normal results or error messages without database errors

📡 Detection & Monitoring

Log Indicators:

  • Unusual database query patterns
  • Multiple failed login attempts after search operations
  • SQL syntax errors in application logs

Network Indicators:

  • HTTP POST requests to /search-report-result.php with SQL keywords in parameters
  • Unusual database connection patterns from web server

SIEM Query:

source="web_logs" AND uri="/search-report-result.php" AND (param="serachdata" AND value MATCHES "(?i)(union|select|insert|delete|update|drop|--|#|\*|' OR ')")

🔗 References

📤 Share & Export