CVE-2025-6884
BaseFortify
Publication date: 2025-06-30
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 |
|---|---|---|
| carmelo | staff_audit_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-6884 is a critical SQL injection vulnerability in version 1.0 of the Staff Audit System, specifically in the /search_index.php file. The vulnerability occurs because the 'search' parameter in POST requests is directly used in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. Various exploitation techniques such as Boolean-based blind, error-based, time-based blind, and UNION-based SQL injection can be used to exploit this flaw. [1]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and potential service disruption. This poses significant risks to system security and business continuity. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'search' parameter in POST requests to /search_index.php for SQL injection. Example payloads to test include Boolean-based blind SQL injection like `search=-9475' OR 1470=1470#`, error-based SQL injection for MySQL ≥ 5.6 such as `search=11' AND GTID_SUBSET(CONCAT(0x717a6a6b71,(SELECT (ELT(3013=3013,1))),0x71706b7171),3013)-- wmrG`, time-based blind SQL injection for MySQL ≥ 5.0.12 like `search=11' AND (SELECT 9975 FROM (SELECT(SLEEP(5)))ydxv)-- UPSC`, and UNION-based SQL injection with a 20-column UNION SELECT statement. Tools like sqlmap can be used to automate detection and exploitation testing. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection; 2) Enforcing strict input validation and filtering to ensure inputs conform to expected formats and block malicious data; 3) Restricting database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations. [1]