CVE-2025-6823
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-6823 is a critical SQL injection vulnerability in version 1.0 of the code-projects Inventory Management System. It exists in the /php_action/editProduct.php file, specifically in the handling of the 'editProductName' parameter. Due to inadequate input validation and sanitization, attackers can inject malicious SQL code remotely without authentication. This allows unauthorized access to the database, enabling attackers to retrieve, modify, or delete sensitive data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data modification, or deletion. Attackers can compromise the confidentiality, integrity, and availability of the system. It may also result in full system compromise or service disruption. Since the exploit requires no authentication and can be performed remotely, it poses a significant risk to business continuity and data security. [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/editProduct.php endpoint for SQL injection in the editProductName parameter. Tools like sqlmap can be used to automate detection, especially using a time-based blind SQL injection payload (e.g., leveraging MySQL SLEEP() function). Additionally, Google dorking with queries such as 'inurl:php_action/editProduct.php' can help identify vulnerable targets. A sample approach is to send multipart form data with malicious SQL payloads in the editProductName parameter and observe the response or timing delays to confirm injection. [2, 3]
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 the editProductName parameter, and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Regular security audits of code and systems should be conducted to detect and address vulnerabilities promptly. If possible, replacing the affected component with an alternative product is also suggested. [2, 3, 1]