CVE-2025-6819
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
Can you explain this vulnerability to me?
CVE-2025-6819 is a critical SQL injection vulnerability in version 1.0 of the code-projects Inventory Management System, specifically in the file /php_action/removeBrand.php. The vulnerability occurs because the brandId parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This improper handling can alter the intended SQL queries, leading to unauthorized database access and manipulation. Exploitation can be done remotely without authentication. [1, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely execute arbitrary SQL commands on your database without any authentication. This can lead to unauthorized access to sensitive data, modification or deletion of data, data leakage, full system control, and potential service disruption. The integrity, confidentiality, and availability of your system can be severely compromised. [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/removeBrand.php endpoint for SQL injection on the brandId parameter. Proof-of-concept tests used boolean-based blind and time-based blind SQL injection techniques. Example payloads include: brandId=(SELECT (CASE WHEN (2248=2248) THEN 1 ELSE (SELECT 7216 UNION SELECT 8038) END)) and brandId=1 AND (SELECT 2526 FROM (SELECT(SLEEP(5)))yYcm). Tools like sqlmap can be used to automate detection, e.g., sqlmap -u "http://target/php_action/removeBrand.php" --data "brandId=1" --technique=B,T. Additionally, Google dorking with the query inurl:php_action/removeBrand.php can help identify vulnerable targets. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replace the affected component or upgrade to a version without the vulnerability if available. 2) Implement prepared statements with parameter binding to prevent SQL injection. 3) Apply strict input validation and filtering on the brandId parameter. 4) Minimize database user permissions by avoiding use of high-privilege accounts for routine operations. 5) Conduct regular security audits to detect and fix vulnerabilities promptly. Since no official patches or countermeasures are published, replacing or securing the affected code is critical. [1, 3, 2]