CVE-2025-6963
BaseFortify
Publication date: 2025-07-01
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 | employee_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-6963 is a critical SQL injection vulnerability in version 1.0 of the Campcodes Employee Management System, specifically in the /myprofile.php file. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized before being used in SQL queries. This allows remote attackers to inject malicious SQL code, which can lead to unauthorized access to the database, data leakage, data manipulation, and potentially full system control without requiring authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized retrieval, modification, or deletion of sensitive data stored in the database. Attackers can manipulate or leak confidential information, disrupt system availability, and potentially gain full control over the affected system. This compromises the confidentiality, integrity, and availability of the system and its data, posing significant security risks. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the 'id' parameter in the /myprofile.php file for SQL injection flaws. Tools like sqlmap can be used to automate detection. Example payloads for manual testing include boolean-based blind, error-based, time-based blind, and UNION query injections, such as: - Boolean-based blind: id=(SELECT (CASE WHEN (9992=9992) THEN 1 ELSE (SELECT 6181 UNION SELECT 2655) END)) - Error-based: id=1 OR (SELECT 6451 FROM(SELECT COUNT(*),CONCAT(0x71627a6b71,(SELECT (ELT(6451=6451,1))),0x716a766a71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) - Time-based blind: id=1 AND (SELECT 9525 FROM (SELECT(SLEEP(5)))gczN) - UNION query: id=1 UNION ALL SELECT CONCAT(0x71627a6b71,0x5872626850526e4955584c71656366514b794c50756e645057746c58437969574272586b6a6d536c,0x716a766a71)-- - Using sqlmap with a command like `sqlmap -u "http://target/myprofile.php?id=1" --batch` can confirm the vulnerability. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to separate SQL code from user input. - Apply strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. - Minimize database user permissions by avoiding use of high-privilege accounts for the application database connection. - Conduct regular security audits to detect and fix vulnerabilities promptly. - If possible, replace the affected component with an alternative product as no known mitigations are documented. These actions help prevent exploitation and protect system security and data integrity. [1, 2, 3]