CVE-2025-13060
📋 TL;DR
This vulnerability allows remote attackers to execute SQL injection attacks against SourceCodester Survey Application System 1.0 via the ID parameter in /view_survey.php. Attackers can potentially read, modify, or delete database content. Organizations using this specific version of the survey application are affected.
💻 Affected Systems
- SourceCodester Survey Application System
📦 What is this software?
⚠️ Risk & Real-World Impact
Worst Case
Complete database compromise including data theft, data manipulation, or complete system takeover if database privileges allow command execution.
Likely Case
Unauthorized data access, data exfiltration, and potential privilege escalation within the application.
If Mitigated
Limited impact with proper input validation, parameterized queries, and database permission restrictions in place.
🎯 Exploit Status
Public exploit available on GitHub; SQL injection is a well-understood attack vector with many automated tools available.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Unknown
Vendor Advisory: https://www.sourcecodester.com/
Restart Required: No
Instructions:
No official patch available. Consider upgrading to a newer version if available or implementing workarounds.
🔧 Temporary Workarounds
Input Validation Filter
allAdd server-side validation to ensure ID parameter contains only numeric values
Modify /view_survey.php to include: if(!is_numeric($_GET['ID'])) { die('Invalid input'); }
Web Application Firewall Rule
allBlock SQL injection patterns targeting the /view_survey.php endpoint
WAF rule: deny requests to /view_survey.php containing SQL keywords in ID parameter
🧯 If You Can't Patch
- Remove or restrict access to /view_survey.php file
- Implement network segmentation to isolate the vulnerable system
🔍 How to Verify
Check if Vulnerable:
Test /view_survey.php with SQL injection payloads like: /view_survey.php?ID=1' OR '1'='1Check Version:
Check application files or documentation for version informationVerify Fix Applied:
Test with same payloads; application should reject or sanitize input without executing SQL📡 Detection & Monitoring
Log Indicators:
- Unusual SQL errors in application logs
- Multiple requests to /view_survey.php with special characters
Network Indicators:
- HTTP requests containing SQL keywords (SELECT, UNION, etc.) in URL parameters
SIEM Query:
source="web_logs" AND url="/view_survey.php" AND (url="*'*" OR url="*SELECT*" OR url="*UNION*")🔗 References
- https://github.com/lakshayyverma/CVE-Discovery/blob/main/Survey%20Application%20System%202%20.md
- https://vuldb.com/?ctiid.332187
- https://vuldb.com/?id.332187
- https://vuldb.com/?submit.682565
- https://www.sourcecodester.com/
- https://github.com/lakshayyverma/CVE-Discovery/blob/main/Survey%20Application%20System%202%20.md
