CVE-2025-6822
BaseFortify
Publication date: 2025-06-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 |
|---|---|---|
| code-projects | inventory_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
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to sensitive data, data tampering, deletion of records, and full compromise of the database. Attackers can remotely execute arbitrary SQL commands, potentially disrupting services and compromising the integrity, confidentiality, and availability of the system. [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/removeProduct.php endpoint for SQL injection in the productId parameter. Detection methods include using SQL injection testing tools like sqlmap with payloads targeting the productId parameter. Example commands include: 1. Using sqlmap: sqlmap -u "http://<target>/inventory-management-system/php_action/removeProduct.php" --data="productId=2" --batch 2. Manual testing with crafted payloads such as: productId=(SELECT (CASE WHEN (9890=9890) THEN 2 ELSE (SELECT 2575 UNION SELECT 4808) END)) productId=2 AND (SELECT 4578 FROM (SELECT(SLEEP(5)))oZKv) Additionally, vulnerable targets can be identified using Google dorking with queries like: inurl:php_action/removeProduct.php [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Use prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection. - Implement strict input validation and filtering to ensure inputs conform to expected formats. - Minimize database user permissions by avoiding high-privilege accounts for routine operations. - Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. - Since no patches or fixes are currently available, consider replacing the vulnerable product with an alternative solution. Applying these measures immediately is necessary to protect system security and maintain data integrity. [1, 2, 3]
Can you explain this vulnerability to me?
CVE-2025-6822 is a critical SQL injection vulnerability in version 1.0 of the code-projects Inventory Management System. It exists in the /php_action/removeProduct.php file due to improper validation and sanitization of the 'productId' parameter. This flaw allows attackers to inject malicious SQL code remotely without authentication, enabling unauthorized access to the database, data leakage, modification, deletion, and potentially full system compromise. [1, 2, 3]