CVE-2025-0527

7.3 HIGH

📋 TL;DR

This critical vulnerability in code-projects Admission Management System 1.0 allows remote attackers to execute SQL injection via the in_eml parameter in /signupconfirm.php, potentially leading to unauthorized data access or manipulation. It affects all users running the default version of this software, particularly those with internet-facing deployments.

💻 Affected Systems

Products:
  • code-projects Admission Management System
Versions: 1.0
Operating Systems: Any OS running PHP and a compatible database (e.g., MySQL)
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability is in the default installation; no special configuration is required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise, including data theft, modification, or deletion, and potential remote code execution if database permissions allow.

🟠

Likely Case

Unauthorized access to sensitive user data (e.g., login credentials, personal information) stored in the database.

🟢

If Mitigated

Limited impact with proper input validation and database hardening, such as restricted database user privileges.

🌐 Internet-Facing: HIGH, as the vulnerability is remotely exploitable and the system is likely exposed to the internet for user sign-ups.
🏢 Internal Only: MEDIUM, as internal attackers could still exploit it, but network segmentation may reduce exposure.

🎯 Exploit Status

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

Exploit details are publicly disclosed, making it easy for attackers to craft SQL injection payloads targeting the in_eml parameter.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not available

Vendor Advisory: https://code-projects.org/

Restart Required: No

Instructions:

No official patch is available. Consider applying manual fixes or workarounds, such as input sanitization in /signupconfirm.php.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Manually modify /signupconfirm.php to validate and sanitize the in_eml parameter using prepared statements or escaping functions.

Edit the PHP file to replace raw SQL queries with parameterized queries using PDO or mysqli.

Web Application Firewall (WAF) Rule

all

Deploy a WAF to block SQL injection attempts targeting the /signupconfirm.php endpoint.

Configure WAF rules to detect and block patterns like SQL keywords in the in_eml parameter.

🧯 If You Can't Patch

  • Disable or restrict access to /signupconfirm.php if not essential for operations.
  • Implement network segmentation to isolate the system and limit exposure to untrusted networks.

🔍 How to Verify

Check if Vulnerable:

Test by sending a crafted SQL injection payload (e.g., ' OR '1'='1) to the in_eml parameter in a POST request to /signupconfirm.php and observe database errors or unexpected behavior.

Check Version:

Check the software version in the system's admin panel or by reviewing the source code files for version indicators.

Verify Fix Applied:

After applying workarounds, retest with the same payload; successful fixes should return normal responses without SQL errors or data leakage.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in web server logs (e.g., PHP warnings related to database queries) for /signupconfirm.php.

Network Indicators:

  • HTTP POST requests to /signupconfirm.php containing SQL keywords (e.g., SELECT, UNION, OR) in the in_eml parameter.

SIEM Query:

source="web_server_logs" AND url="/signupconfirm.php" AND (payload CONTAINS "' OR" OR payload CONTAINS "UNION" OR payload CONTAINS "SELECT")

🔗 References

📤 Share & Export