CVE-2025-10025

7.3 HIGH

📋 TL;DR

This SQL injection vulnerability in PHPGurukul Online Course Registration 3.1 allows attackers to manipulate database queries through the semester parameter in /admin/semester.php. Attackers can potentially read, modify, or delete database content. Organizations using this specific version of the software are affected.

💻 Affected Systems

Products:
  • PHPGurukul Online Course Registration
Versions: 3.1
Operating Systems: All platforms running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Requires the /admin/semester.php endpoint to be accessible. The vulnerability is in the core application code.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data manipulation, or deletion; potential privilege escalation to administrative access; possible remote code execution if database configuration permits.

🟠

Likely Case

Unauthorized data access and extraction from the database, potentially exposing sensitive user information, course registrations, and administrative data.

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available on GitHub. Attack requires access to the admin interface but SQL injection is straightforward once authenticated.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://phpgurukul.com/

Restart Required: No

Instructions:

1. Check vendor website for security updates. 2. If patch available, download and apply. 3. Test functionality after patching. 4. No official patch currently available.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement proper input validation and parameterized queries for the semester parameter

Modify /admin/semester.php to use prepared statements with parameterized queries

Access Restriction

all

Restrict access to the vulnerable endpoint

Add authentication/authorization checks or IP restrictions to /admin/semester.php

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block SQL injection patterns targeting the semester parameter
  • Restrict network access to the application to trusted IP addresses only

🔍 How to Verify

Check if Vulnerable:

Check if /admin/semester.php exists and accepts semester parameter without proper input validation

Check Version:

Check application version in admin panel or configuration files

Verify Fix Applied:

Test the semester parameter with SQL injection payloads to confirm they are properly sanitized or blocked

📡 Detection & Monitoring

Log Indicators:

  • Unusual database queries from web application logs
  • Multiple failed login attempts followed by SQL injection attempts
  • Unexpected database errors in application logs

Network Indicators:

  • HTTP requests to /admin/semester.php with SQL keywords in parameters
  • Unusual database connection patterns from web server

SIEM Query:

web.url:"/admin/semester.php" AND (web.param:"semester" AND (web.param.value:"UNION" OR web.param.value:"SELECT" OR web.param.value:"OR 1=1"))

🔗 References

📤 Share & Export