CVE-2025-8950
7.3Campcodes · Online Recruitment Management System
Campcodes Online Recruitment Management System 1.0 is vulnerable to remote SQL injection via the ID parameter in the view_vacancy page, allowing unauthenticated attackers to manipulate database queries.
Executive summary
A critical SQL injection vulnerability in Campcodes Online Recruitment Management System 1.0 allows unauthenticated remote attackers to compromise database integrity and potentially exfiltrate sensitive data.
Vulnerability
The application fails to properly sanitize the ID argument within the Recruitment/index.php?page=view_vacancy endpoint. This SQL injection flaw can be triggered remotely by an unauthenticated attacker to manipulate backend database operations.
Business impact
Successful exploitation of this vulnerability permits unauthorized database interaction, which may lead to the exposure of applicant data, credentials, or other sensitive recruitment information. Given the CVSS score of 7.3, this represents a high-severity risk that could result in significant data breaches and a loss of organizational trust.
Remediation
Immediate Action: As no official patch is currently available, administrators should restrict access to the affected recruitment portal or implement strict input validation rules to block malicious SQL syntax.
Proactive Monitoring: Review web server access logs for suspicious patterns in URL parameters, specifically looking for SQL keywords or anomalous character sequences directed at the view_vacancy page.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection payloads targeting the identified vulnerable parameter.
Exploitation status
Public Exploit Available: Yes, a published proof-of-concept exists as documented in the GitHub issue referenced in the vulnerability record.
Analyst recommendation
Due to the public availability of exploit code and the lack of an official vendor patch, this vulnerability poses a significant risk to any organization running the affected software. Security teams must prioritize isolating the vulnerable system from public access or applying robust WAF filtering to prevent unauthorized database access until a formal security update is released by the vendor.
Sources
Originally found and disclosed by noc13 (VulDB User), per the CVE Program record.