CVE-2025-11659

7.3 HIGH

📋 TL;DR

This vulnerability allows remote attackers to upload arbitrary files to the ProjectsAndPrograms School Management System via the /assets/uploadNotes.php endpoint. This unrestricted file upload flaw can lead to remote code execution or system compromise. All instances running versions up to commit 6b6fae5426044f89c08d0dd101c7fa71f9042a59 are affected.

💻 Affected Systems

Products:
  • ProjectsAndPrograms School Management System
Versions: All versions up to commit 6b6fae5426044f89c08d0dd101c7fa71f9042a59
Operating Systems: Any OS running the web application
Default Config Vulnerable: ⚠️ Yes
Notes: The product follows rolling release delivery, making specific version numbers unavailable. The vulnerability exists in the upload functionality.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete system takeover, data exfiltration, ransomware deployment, or creation of persistent backdoors.

🟠

Likely Case

Attackers upload web shells to gain unauthorized access, deface websites, or steal sensitive student/administrative data.

🟢

If Mitigated

File uploads are blocked or properly validated, preventing malicious file execution while maintaining legitimate functionality.

🌐 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, making this easily exploitable by attackers with basic skills.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None found

Restart Required: No

Instructions:

1. Check for updates from the ProjectsAndPrograms repository. 2. Apply any available patches. 3. Verify the fix by testing file upload functionality.

🔧 Temporary Workarounds

Block uploadNotes.php endpoint

all

Temporarily disable the vulnerable upload functionality

# Apache: RewriteRule ^/assets/uploadNotes\.php$ - [F]
# Nginx: location ~ /assets/uploadNotes\.php$ { deny all; }

Implement file upload restrictions

all

Add server-side validation for file types and sizes

# Example PHP validation: $allowed_types = ['pdf', 'doc', 'txt']; $max_size = 5242880;

🧯 If You Can't Patch

  • Implement a Web Application Firewall (WAF) with rules to block malicious file uploads
  • Restrict access to the /assets/ directory and monitor for suspicious upload attempts

🔍 How to Verify

Check if Vulnerable:

Attempt to upload a file with a malicious extension (e.g., .php, .jsp) to /assets/uploadNotes.php. If accepted without validation, the system is vulnerable.

Check Version:

Check the git commit hash or version file in the application directory

Verify Fix Applied:

Test file upload functionality with various file types. Only allowed file types should be accepted, and malicious extensions should be rejected.

📡 Detection & Monitoring

Log Indicators:

  • Unusual file uploads to /assets/uploadNotes.php
  • Uploads of executable file types (.php, .jsp, .exe)
  • Multiple failed upload attempts

Network Indicators:

  • POST requests to /assets/uploadNotes.php with suspicious file names
  • Traffic patterns indicating file upload exploitation

SIEM Query:

source="web_logs" AND uri="/assets/uploadNotes.php" AND (file_extension="php" OR file_extension="jsp" OR file_extension="exe")

🔗 References

📤 Share & Export