CVE-2025-11585

7.3 HIGH

📋 TL;DR

This vulnerability allows remote attackers to execute SQL injection attacks against Project Monitoring System 1.0 through the uid parameter in /useredit.php. This could lead to unauthorized data access, modification, or deletion. Organizations using this specific software version are affected.

💻 Affected Systems

Products:
  • code-projects Project Monitoring System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default installation of version 1.0. No special configuration is required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, or full system takeover through SQL injection leading to remote code execution.

🟠

Likely Case

Unauthorized access to sensitive user data, modification of user accounts, or privilege escalation within the application.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only error messages or minor data exposure.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

The exploit has been made public according to the CVE description, making it easily accessible to attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

1. Check code-projects.org for security updates. 2. If no patch is available, implement workarounds. 3. Consider migrating to alternative software if no fix is forthcoming.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement proper input validation and parameterized queries for the uid parameter in /useredit.php

Modify /useredit.php to use prepared statements: $stmt = $conn->prepare('SELECT * FROM users WHERE id = ?'); $stmt->bind_param('i', $uid);

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection protection rules

🧯 If You Can't Patch

  • Isolate the system from the internet and restrict access to authorized users only
  • Implement network segmentation and monitor all traffic to/from the vulnerable system

🔍 How to Verify

Check if Vulnerable:

Check if /useredit.php exists and accepts uid parameter without proper input validation. Test with SQL injection payloads like: ' OR '1'='1

Check Version:

Check the software version in the application interface or configuration files

Verify Fix Applied:

Test the uid parameter with SQL injection payloads after applying fixes. Verify no database errors or unexpected behavior occurs.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts or parameter manipulation in web server logs
  • Unexpected database errors in application logs

Network Indicators:

  • HTTP requests to /useredit.php with SQL injection patterns in parameters
  • Unusual database connection patterns from web server

SIEM Query:

source="web_logs" AND uri="/useredit.php" AND (param="uid" AND value MATCHES "('|--|;|UNION|SELECT)")

🔗 References

📤 Share & Export