CVE-2025-5676
BaseFortify
Publication date: 2025-06-05
Last updated on: 2025-06-10
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-5676 is a critical SQL injection vulnerability in Campcodes Online Recruitment Management System version 1.0. It occurs in the /admin/ajax.php?action=login endpoint due to improper handling and insufficient validation of the 'username' parameter. This flaw allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized access to the database, data leakage, modification, or deletion of sensitive information. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, exposure of sensitive data, data manipulation, deletion, and potentially full system compromise or service disruption. Since it requires no authentication and can be exploited remotely, it poses a severe risk to system security and business continuity. [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 /Recruitment/admin/ajax.php?action=login endpoint for SQL injection in the 'username' parameter. You can use SQL injection testing tools like sqlmap to automate detection. Example commands include: 1. Using sqlmap: sqlmap -u "http://target/Recruitment/admin/ajax.php?action=login" --data="username=admin&password=any" --risk=3 --level=5 --batch 2. Manual testing with curl and payloads: curl -X POST -d "username=admin' AND 1=1-- &password=any" http://target/Recruitment/admin/ajax.php?action=login curl -X POST -d "username=admin' AND 1=2-- &password=any" http://target/Recruitment/admin/ajax.php?action=login 3. Boolean-based blind SQL injection payloads: username=admin' AND 7712=7712 AND 'VZHW'='VZHW 4. Time-based blind SQL injection payloads: username=admin' AND (SELECT SLEEP(5))-- These tests can help confirm the presence of the SQL injection vulnerability by observing differences in responses or delays. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Implement prepared statements with parameterized queries to separate SQL code from user input, preventing injection. 2. Apply strict input validation and filtering on the 'username' parameter to ensure it conforms to expected formats. 3. Minimize database user privileges by avoiding high-privilege accounts for routine database operations. 4. Conduct regular security audits and code reviews to detect and fix vulnerabilities promptly. If possible, consider replacing the affected product or applying vendor patches once available to fully remediate the issue. [2]