CVE-2025-8274
BaseFortify
Publication date: 2025-07-28
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-8274 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 parameter is set to save_recruitment_status. The vulnerability arises because the ID parameter is not properly sanitized, allowing attackers to inject malicious SQL code. This improper handling enables attackers to manipulate the SQL queries executed by the system, potentially leading to unauthorized database access and control. [1, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact the confidentiality, integrity, and availability of your system. An attacker can remotely exploit it without authentication to inject SQL commands, which may allow them to retrieve sensitive information, modify or delete data, gain full control over the system, and disrupt services. The exploit is publicly available, making it easier for attackers to launch attacks against vulnerable systems. [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 vulnerable endpoint `/Recruitment/admin/ajax.php?action=save_recruitment_status` with specially crafted SQL injection payloads targeting the `id` parameter. A boolean-based blind SQL injection payload can be sent via a multipart POST request to check for injection flaws. For example, using curl or similar tools to send a POST request with the payload: ``` ------WebKitFormBoundaryNmloDDWxZzlxWqBy Content-Disposition: form-data; name="id" (SELECT (CASE WHEN (1148=1148) THEN '' ELSE (SELECT 3247 UNION SELECT 3910) END)) ------WebKitFormBoundaryNmloDDWxZzlxWqBy Content-Disposition: form-data; name="status_label" 11 ------WebKitFormBoundaryNmloDDWxZzlxWqBy-- ``` Alternatively, automated tools like sqlmap can be used to test and confirm the SQL injection vulnerability by targeting the `id` parameter in the POST data to extract database information. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Replace the affected product with an alternative solution if possible, as no known countermeasures are documented. 2. Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 3. Apply strict input validation and filtering on the `id` parameter to ensure it conforms to expected formats. 4. Minimize database user permissions by avoiding use of high-privilege accounts for routine database operations. 5. Conduct regular security audits of the code and system to detect and fix vulnerabilities promptly. These steps help reduce the risk of exploitation until a secure patch or update is available. [1, 3]