CVE-2025-6612
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-6612 is a critical SQL injection vulnerability in version 1.0 of the code-projects Inventory Management System. It occurs in the /php_action/removeCategories.php file due to improper handling and insufficient validation of the 'categoriesId' parameter. This flaw allows attackers to inject malicious SQL code remotely without authentication, enabling unauthorized database access, data modification, deletion, or exposure of sensitive information. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, leakage of sensitive data, modification or deletion of records, potential full system control by attackers, and service disruptions. Since no authentication is required, attackers can remotely exploit this flaw easily, posing a severe risk to system security and data integrity. [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/removeCategories.php endpoint for SQL injection via the categoriesId parameter. Proof-of-concept payloads include boolean-based blind and time-based blind SQL injection techniques. Example commands using sqlmap are effective for detection, such as: sqlmap -u "http://target/php_action/removeCategories.php" --data="categoriesId=1" --technique=B,T Additionally, manual testing with payloads like categoriesId=(SELECT (CASE WHEN (2857=2857) THEN 1 ELSE (SELECT 3628 UNION SELECT 3439) END)) or categoriesId=1 AND (SELECT 8120 FROM (SELECT(SLEEP(5)))JIDL) can confirm the vulnerability by observing response differences or delays. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to separate SQL code from user input. - Apply strict input validation and filtering on the categoriesId parameter to ensure only expected values are accepted. - Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts. - Conduct regular security audits of the code and system. Since no vendor patch is currently available, these measures are critical to reduce risk until a fix or alternative product is deployed. [2, 3]