CVE-2025-7135
BaseFortify
Publication date: 2025-07-07
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| campcodes | online_recruitment_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7135 is a critical SQL injection vulnerability in Campcodes Online Recruitment Management System version 1.0. It occurs in the file /admin/ajax.php when the action=save_vacancy parameter is used. The vulnerability arises because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized access to the database, enabling attackers to view, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to remotely exploit the system without any authentication. They can inject SQL commands to access sensitive information, modify or delete data, and potentially disrupt or fully compromise the system. This threatens the confidentiality, integrity, and availability of your data and services. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /admin/ajax.php endpoint with the parameter action=save_vacancy for SQL injection via the id parameter. A boolean-based blind SQL injection payload can be used, such as: id=(SELECT (CASE WHEN (8126=8126) THEN 2 ELSE (SELECT 4268 UNION SELECT 1226) END)). Additionally, tools like sqlmap can be used to automate detection by sending crafted POST requests to the vulnerable endpoint to enumerate databases and confirm injection points. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to separate SQL code from user input, preventing injection; 2) Implementing strict input validation and filtering to ensure parameters conform to expected formats; 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts like root or admin for routine operations; 4) Conducting regular security audits of code and systems to detect and address vulnerabilities promptly. Since no known patches or countermeasures exist, replacing the affected product with an alternative solution is also suggested. [2, 3]