CVE-2025-6500
BaseFortify
Publication date: 2025-06-23
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-6500 is a critical SQL injection vulnerability in the code-projects Inventory Management System version 1.0. It exists in the file /php_action/editCategories.php due to improper handling and insufficient validation of the 'editCategoriesName' parameter. This flaw allows attackers to inject malicious SQL queries remotely without authentication, potentially enabling unauthorized access to the database, data leakage, modification, or deletion. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, exposure of sensitive information, data modification or deletion, and potentially full system compromise or service disruption. Since it can be exploited remotely without authentication, it poses a significant risk to system security and business continuity. [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 vulnerable endpoint /php_action/editCategories.php for SQL injection on the 'editCategoriesName' parameter. A proof-of-concept payload uses a time-based blind SQL injection technique, for example: editCategoriesName=1111' AND (SELECT 4118 FROM (SELECT(SLEEP(5)))VcjL) AND 'kbXv'='kbXv&editCategoriesStatus=1&editCategoriesId=1. You can use tools like sqlmap to automate detection by targeting this endpoint and parameter. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:php_action/editCategories.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Apply strict input validation and filtering on the 'editCategoriesName' parameter to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like root or admin for routine operations. 4) Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. If possible, replace the affected component with a secure alternative. [1, 2, 3]