CVE-2025-9595
📋 TL;DR
This vulnerability allows attackers to inject malicious scripts into the Student Information Management System login page through the 'uname' parameter. When exploited, it enables cross-site scripting attacks that could steal user credentials or session cookies. Organizations using code-projects Student Information Management System 1.0 are affected.
💻 Affected Systems
- code-projects Student Information Management System
📦 What is this software?
⚠️ Risk & Real-World Impact
Worst Case
Attackers could steal administrator credentials, hijack user sessions, deface the application, or redirect users to malicious sites, potentially leading to complete system compromise.
Likely Case
Attackers will steal user session cookies or credentials, enabling unauthorized access to student information and system functionality.
If Mitigated
With proper input validation and output encoding, the impact is limited to failed exploitation attempts with no data compromise.
🎯 Exploit Status
The exploit is publicly available and requires minimal technical skill to execute against vulnerable systems.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Unknown
Vendor Advisory: https://code-projects.org/
Restart Required: No
Instructions:
No official patch available. Consider implementing input validation and output encoding in /login.php, or replace with alternative software.
🔧 Temporary Workarounds
Implement Input Validation
allAdd server-side validation to sanitize the 'uname' parameter in /login.php
Edit /login.php to add: $uname = htmlspecialchars($_POST['uname'], ENT_QUOTES, 'UTF-8');
Web Application Firewall (WAF)
allDeploy a WAF with XSS protection rules to filter malicious input
🧯 If You Can't Patch
- Isolate the system behind a reverse proxy with XSS filtering capabilities
- Implement strict Content Security Policy (CSP) headers to mitigate script execution
🔍 How to Verify
Check if Vulnerable:
Test by submitting <script>alert('XSS')</script> in the username field during login and check if script executesCheck Version:
Check the software version in the application interface or configuration filesVerify Fix Applied:
After implementing fixes, test with the same payload to confirm script does not execute📡 Detection & Monitoring
Log Indicators:
- Unusual length or special characters in username field entries
- Multiple failed login attempts with script-like patterns
Network Indicators:
- HTTP requests to /login.php containing script tags or JavaScript in POST parameters
SIEM Query:
source="web_logs" AND uri_path="/login.php" AND (request_body CONTAINS "<script>" OR request_body CONTAINS "javascript:")