CVE-2025-6901
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 |
|---|---|---|
| code-projects | inventory_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-6901 is a critical SQL injection vulnerability in version 1.0 of the code-projects Inventory Management System, specifically in the /php_action/removeUser.php file. The vulnerability arises from improper handling and insufficient sanitization of the 'userid' parameter, which allows an attacker to inject malicious SQL code remotely without authentication. This can lead to unauthorized manipulation of SQL queries, impacting the confidentiality, integrity, and availability of the system. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to gain unauthorized access to the database, leading to data leakage, unauthorized data modification or deletion, full system compromise, and disruption of services. Since exploitation requires no authentication and can be performed remotely, it poses a high risk to system security and data integrity. [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 /php_action/removeUser.php endpoint for SQL injection via the 'userid' parameter. One can use tools like sqlmap to automate detection, for example: sqlmap -u "http://<target>/php_action/removeUser.php" --data="userid=1" --risk=3 --level=5. Additionally, manual testing with payloads such as boolean-based blind SQL injection (e.g., userid=(SELECT (CASE WHEN (3639=3639) THEN 11 ELSE (SELECT 6611 UNION SELECT 2378) END))) or time-based blind SQL injection (e.g., userid=11 AND 5136=BENCHMARK(5000000,MD5(0x6f657765))) can be used to confirm the vulnerability. Google dorking with queries like inurl:php_action/removeUser.php can help identify vulnerable targets on the network. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected component or upgrading to a secure version if available. 2) Implementing prepared statements with parameter binding to separate SQL code from user input. 3) Applying strict input validation and filtering on the 'userid' parameter to ensure it conforms to expected formats. 4) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations. 5) Conducting regular security audits of code and systems to detect and remediate vulnerabilities promptly. Since no known mitigations are documented, these best practices are critical to protect system security and data integrity. [1, 2, 3]