CVE-2025-7134
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7134 is a critical SQL injection vulnerability in Campcodes Online Recruitment Management System version 1.0. It occurs in the file /admin/ajax.php when processing the parameter action=delete_application with the argument id. Due to improper validation and sanitization of the id parameter, attackers can inject malicious SQL queries. This allows unauthorized access to the database, enabling attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact the confidentiality, integrity, and availability of your system. Attackers can remotely exploit it without authentication to access sensitive information, modify or delete database records, and potentially disrupt service availability. This could lead to data breaches, loss of critical data, and unauthorized control over the affected system. [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=delete_application and manipulating the id parameter to check for SQL injection. A proof-of-concept uses a boolean-based blind SQL injection payload in a POST request, for example: id=(SELECT (CASE WHEN (8126=8126) THEN 2 ELSE (SELECT 4268 UNION SELECT 1226) END)). Additionally, the sqlmap tool can be used to automate detection of this SQL injection vulnerability against the affected endpoint. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the id parameter, and limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. Regular security audits of code and systems are also recommended. Since no known mitigations or countermeasures are identified, replacing the affected product with an alternative solution is suggested if immediate patching is not feasible. [2, 3]