CVE-2025-6821
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-6821 is a critical SQL injection vulnerability in version 1.0 of the code-projects Inventory Management System, specifically in the '/php_action/createOrder.php' file. The vulnerability occurs because the system improperly handles a user-supplied parameter ('Array-like #4*' or 'productName[]') without adequate validation or sanitization, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, data leakage, data manipulation, and potential full system control by attackers. It can lead to modification or deletion of critical data, disruption of services, and compromise of system integrity and confidentiality. Since it requires no authentication and is remotely exploitable, attackers can easily exploit it to cause significant damage to the affected 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/createOrder.php' endpoint for SQL injection, particularly targeting the 'productName[]' POST parameter. Tools like sqlmap can be used to automate detection and exploitation attempts. Example command using sqlmap: sqlmap -u "http://target/php_action/createOrder.php" --data="productName[]=test" --risk=3 --level=5 --batch. Additionally, manual testing with boolean-based blind, error-based, and time-based SQL injection payloads can be performed to confirm the vulnerability. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on all user-supplied data, and minimizing database user privileges by avoiding high-privilege accounts for routine operations. Regular security audits should be conducted to detect and address vulnerabilities promptly. If possible, replace or patch the affected component '/php_action/createOrder.php' to remove the vulnerability. [2, 3]