CVE-2025-6841
BaseFortify
Publication date: 2025-06-29
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 |
|---|---|---|
| fabian | product_inventory_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-6841 is a critical SQL injection vulnerability in the Product Inventory System version 1.0, specifically in the /admin/edit_product.php file. It occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can be exploited remotely by authenticated users to manipulate database queries, potentially extracting, modifying, or deleting sensitive data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to the database, data leakage, data tampering, and system compromise. Attackers can modify or delete data, extract sensitive information, and potentially disrupt services, posing significant risks 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 /admin/edit_product.php endpoint with SQL injection payloads targeting the 'id' parameter. For example, boolean-based blind SQL injection can be tested using a URL like: http://localhost/cve/ProductInventorySystem_PHP/feeds/admin/edit_product.php?id=(SELECT (CASE WHEN (2455=2455) THEN 1 ELSE (SELECT 3597 UNION SELECT 3254) END)). Time-based blind SQL injection can be tested with: http://localhost/cve/ProductInventorySystem_PHP/feeds/admin/edit_product.php?id=1 AND (SELECT 4807 FROM (SELECT(SLEEP(5)))vJMn). Additionally, the sqlmap tool can be used with a valid PHPSESSID cookie for authenticated testing, e.g., sqlmap -u "http://target/admin/edit_product.php?id=1" --cookie="PHPSESSID=your_session_id" --batch. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implement strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding high-privilege accounts for routine operations. 4) Conduct regular security audits of the code and system to detect and fix vulnerabilities promptly. If possible, replace the affected component with an alternative product as no known countermeasures are documented. [2, 3, 1]