CVE-2025-1966

7.3 HIGH

📋 TL;DR

A critical SQL injection vulnerability exists in PHPGurukul Pre-School Enrollment System 1.0, specifically in the /admin/index.php file's username parameter. This allows remote attackers to execute arbitrary SQL commands, potentially compromising the database. All deployments of version 1.0 are affected.

💻 Affected Systems

Products:
  • PHPGurukul Pre-School Enrollment System
Versions: 1.0
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability is in the default installation and requires no special configuration to be exploitable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data manipulation, authentication bypass, and potential remote code execution via database functions.

🟠

Likely Case

Unauthorized access to sensitive student and administrative data, including personal information, enrollment records, and potentially authentication credentials.

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details have been publicly disclosed, making this easily exploitable by attackers with basic SQL injection knowledge.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not available

Vendor Advisory: https://phpgurukul.com/

Restart Required: No

Instructions:

No official patch is available. Apply input validation and parameterized queries to the /admin/index.php file's username parameter.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement strict input validation for the username parameter to reject SQL injection attempts.

Modify /admin/index.php to validate username input using regex or whitelist acceptable characters

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection protection rules to block exploitation attempts.

🧯 If You Can't Patch

  • Isolate the system from the internet and restrict access to trusted networks only.
  • Implement network segmentation and strict access controls to limit potential lateral movement.

🔍 How to Verify

Check if Vulnerable:

Test the /admin/index.php endpoint with SQL injection payloads in the username parameter (e.g., ' OR '1'='1).

Check Version:

Check the system version in the application's admin panel or configuration files.

Verify Fix Applied:

Verify that SQL injection attempts no longer succeed and that input validation is properly implemented.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Failed login attempts with SQL syntax in username field
  • Multiple requests to /admin/index.php with suspicious parameters

Network Indicators:

  • HTTP requests to /admin/index.php containing SQL keywords (SELECT, UNION, etc.) in parameters

SIEM Query:

source="web_logs" AND uri="/admin/index.php" AND (username="*SELECT*" OR username="*UNION*" OR username="*OR*" OR username="*--*")

🔗 References

📤 Share & Export