CVE-2025-8471

7.3 HIGH

📋 TL;DR

This critical SQL injection vulnerability in projectworlds Online Admission System 1.0 allows attackers to manipulate database queries through the a_id parameter in /adminlogin.php. Attackers can potentially read, modify, or delete database contents, and may gain administrative access. All deployments of version 1.0 are affected.

💻 Affected Systems

Products:
  • projectworlds Online Admission System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of version 1.0 are vulnerable by default

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, system takeover, and potential lateral movement to other systems

🟠

Likely Case

Unauthorized data access, credential theft, and privilege escalation to admin level

🟢

If Mitigated

Limited impact with proper input validation and database permissions

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available on GitHub

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None found

Restart Required: No

Instructions:

No official patch available. Consider upgrading to a newer version if available or implementing workarounds.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement proper input validation and parameterized queries for the a_id parameter

Modify /adminlogin.php to use prepared statements: $stmt = $conn->prepare('SELECT * FROM admin WHERE a_id = ?'); $stmt->bind_param('s', $a_id);

Web Application Firewall (WAF)

all

Deploy WAF rules to block SQL injection patterns

Add WAF rule: SecRule ARGS:a_id "@detectSQLi" "id:1001,phase:2,deny,status:403"

🧯 If You Can't Patch

  • Isolate the system behind a firewall with strict access controls
  • Implement network segmentation to limit potential lateral movement

🔍 How to Verify

Check if Vulnerable:

Test /adminlogin.php with SQL injection payloads in a_id parameter

Check Version:

Check system documentation or configuration files for version information

Verify Fix Applied:

Verify that SQL injection attempts no longer succeed and proper input validation is in place

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts with SQL patterns

Network Indicators:

  • HTTP requests to /adminlogin.php with SQL keywords in parameters

SIEM Query:

source="web_logs" AND uri="/adminlogin.php" AND (param="a_id" AND value MATCHES "(?i)(union|select|insert|delete|update|drop|--|#|;)")

🔗 References

📤 Share & Export