CVE-2025-2675

7.3 HIGH

📋 TL;DR

This critical SQL injection vulnerability in PHPGurukul Bank Locker Management System 1.0 allows attackers to execute arbitrary SQL commands via the lockerprice parameter in /add-lockertype.php. Attackers can potentially access, modify, or delete database content including sensitive locker management data. The vulnerability affects all systems running this specific software version.

💻 Affected Systems

Products:
  • PHPGurukul Bank Locker Management System
Versions: 1.0
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the specific file /add-lockertype.php; requires PHP environment with database connectivity.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data manipulation, or complete system takeover through privilege escalation.

🟠

Likely Case

Unauthorized access to sensitive bank locker customer data, financial information, and system configuration details.

🟢

If Mitigated

Limited impact with proper input validation and database permissions restricting damage to non-critical data.

🌐 Internet-Facing: HIGH - Attack can be launched remotely without authentication, making internet-facing instances extremely vulnerable.
🏢 Internal Only: MEDIUM - Internal systems still vulnerable but require network access; risk reduced by network segmentation.

🎯 Exploit Status

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

Exploit details are publicly disclosed; SQL injection is well-understood with many automated tools available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://phpgurukul.com/

Restart Required: No

Instructions:

No official patch available. Contact vendor for updated version or implement workarounds.

🔧 Temporary Workarounds

Input Validation and Sanitization

PHP

Implement proper input validation and parameterized queries for the lockerprice parameter

Modify /add-lockertype.php to use prepared statements: $stmt = $conn->prepare('INSERT INTO lockertype (lockerprice) VALUES (?)'); $stmt->bind_param('s', $lockerprice);

Web Application Firewall (WAF)

all

Deploy WAF rules to block SQL injection patterns targeting /add-lockertype.php

🧯 If You Can't Patch

  • Block external access to /add-lockertype.php via firewall rules or web server configuration
  • Implement database user with minimal permissions (read-only where possible) for the application

🔍 How to Verify

Check if Vulnerable:

Test /add-lockertype.php with SQL injection payloads in lockerprice parameter (e.g., ' OR '1'='1)

Check Version:

Check software version in admin panel or configuration files

Verify Fix Applied:

Verify that SQL injection payloads no longer execute and return proper error handling

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts following SQL injection patterns
  • Access to /add-lockertype.php with suspicious parameters

Network Indicators:

  • HTTP POST requests to /add-lockertype.php containing SQL keywords in parameters
  • Unusual database connection patterns from web server

SIEM Query:

source="web_logs" AND url="/add-lockertype.php" AND (param="lockerprice" AND value MATCHES "('|\"|OR|UNION|SELECT)")

🔗 References

📤 Share & Export