CVE-2025-6611
BaseFortify
Publication date: 2025-06-25
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
Can you explain this vulnerability to me?
CVE-2025-6611 is a critical SQL injection vulnerability in version 1.0 of the code-projects Inventory Management System. It occurs in the /php_action/createBrand.php file due to improper handling of the 'brandStatus' parameter, which is not properly validated or sanitized. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, modification, or deletion. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, exposure of sensitive information, modification or deletion of data, and potentially full system compromise or service disruption. Since the attack can be performed remotely without authentication, it poses a significant risk to data confidentiality, integrity, and availability. [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/createBrand.php endpoint for SQL injection on the brandStatus parameter. A proof-of-concept uses a time-based blind SQL injection payload such as: brandName=qq&brandStatus=1' AND (SELECT 1659 FROM (SELECT(SLEEP(5)))SVRH) AND 'dLAD'='dLAD, which causes a delay in the database response. Tools like sqlmap can be used to automate detection against this endpoint. Additionally, vulnerable targets can be identified using Google dorking with queries like: inurl:php_action/createBrand.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implement strict input validation and filtering on the brandStatus parameter to ensure it conforms to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, replace the affected component with an alternative product. [1, 2, 3]