CVE-2025-11584
7.3code-projects · Online Job Search Engine
A SQL injection vulnerability in the Online Job Search Engine 1.0 allows unauthenticated attackers to manipulate the txtspecialization argument in searchjob.php to execute arbitrary SQL commands.
Executive summary
A critical SQL injection vulnerability in the code-projects Online Job Search Engine 1.0 permits unauthenticated remote code execution or data extraction via the searchjob.php script.
Vulnerability
This vulnerability is a classic SQL injection flaw (CWE-89) located in the searchjob.php file. An unauthenticated attacker can supply malicious input via the txtspecialization parameter to bypass security controls and interact directly with the backend database.
Business impact
The ability for an unauthenticated user to perform SQL injection poses a significant risk to data confidentiality and integrity. Successful exploitation could lead to unauthorized access to sensitive applicant or employer data, modification of search results, or potential compromise of the underlying server. With a CVSS score of 7.3, this high-severity flaw requires immediate remediation to prevent unauthorized database access.
Remediation
Immediate Action: Since no official vendor patch is currently available, administrators should restrict access to the application or disable the vulnerable searchjob.php functionality until the vendor releases a security update.
Proactive Monitoring: Monitor database query logs for unusual patterns, such as the presence of SQL syntax keywords or unexpected characters within the txtspecialization parameter.
Compensating Controls: Deploy a Web Application Firewall (WAF) with specific rules designed to detect and block SQL injection payloads targeting the searchjob.php endpoint.
Exploitation status
Public Exploit Available: Yes, a public proof-of-concept exists as documented in the referenced GitHub issue.
Analyst recommendation
Given the availability of public proof-of-concept material and the ease of exploitation through an unauthenticated network vector, organizations running this software are at elevated risk. We strongly recommend isolating the affected instance from public networks and applying vendor-supplied security updates the moment they become available to mitigate the threat of database compromise.
More code-projects CVEs
Sources
Originally found and disclosed by xupeng (VulDB User), per the CVE Program record.