CVE-2025-14590
📋 TL;DR
This vulnerability allows remote attackers to execute arbitrary SQL commands via the 'keyname' parameter in the /admin/search1.php file of Prison Management System 2.0. Attackers can potentially access, modify, or delete database content. All users running Prison Management System 2.0 with the vulnerable component exposed are affected.
💻 Affected Systems
- Prison Management System
📦 What is this software?
⚠️ Risk & Real-World Impact
Worst Case
Complete database compromise leading to data theft, data destruction, or full system takeover via SQL injection to execute arbitrary commands.
Likely Case
Unauthorized data access, privilege escalation, or data manipulation within the prison management database.
If Mitigated
Limited impact with proper input validation, parameterized queries, and network segmentation in place.
🎯 Exploit Status
Public exploit code available on GitHub, making exploitation straightforward for attackers.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Unknown
Vendor Advisory: https://code-projects.org/
Restart Required: No
Instructions:
No official patch available. Implement workarounds or migrate to alternative software.
🔧 Temporary Workarounds
Input Validation Filter
allAdd input validation to sanitize the 'keyname' parameter before processing.
Modify /admin/search1.php to validate/sanitize user input for 'keyname' parameter
Parameterized Query Implementation
allRewrite SQL queries to use prepared statements with parameterized queries.
Replace dynamic SQL queries with prepared statements in /admin/search1.php
🧯 If You Can't Patch
- Block external access to /admin/search1.php using firewall rules or web server configuration.
- Implement network segmentation to isolate the Prison Management System from critical networks.
🔍 How to Verify
Check if Vulnerable:
Test /admin/search1.php with SQL injection payloads in the 'keyname' parameter and observe database errors or unexpected behavior.Check Version:
Check software version in application interface or configuration files.Verify Fix Applied:
Retest with SQL injection payloads after implementing fixes; successful fixes should reject malicious input without database errors.📡 Detection & Monitoring
Log Indicators:
- Unusual SQL error messages in application logs
- Multiple failed login attempts or unusual search patterns
Network Indicators:
- HTTP requests to /admin/search1.php with SQL keywords in parameters
- Unusual database query patterns from web server
SIEM Query:
source="web_logs" AND uri="/admin/search1.php" AND (param="keyname" AND value CONTAINS "UNION" OR value CONTAINS "SELECT" OR value CONTAINS "' OR '")