CVE-2025-10417
BaseFortify
Publication date: 2025-09-15
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 |
|---|---|---|
| campcodes | grocery_sales_and_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-10417 is a critical SQL injection vulnerability in Campcodes Grocery Sales and Inventory System version 1.0. It exists in the /ajax.php file when the action=delete_product parameter is used. The vulnerability arises because the 'id' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially manipulating the database in unauthorized ways. [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, data tampering, deletion or modification of data, full system control, and disruption of services. Since no authentication is required, attackers can remotely exploit this flaw, posing severe 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 /ajax.php endpoint with the parameter action=delete_product and manipulating the id parameter to check for SQL injection. A common approach is to use automated tools like sqlmap to test for SQL injection vulnerabilities. For example, you can run a command such as: sqlmap -u "http://target/ajax.php?action=delete_product" --data="id=1" --method=POST to test if the id parameter is injectable. Additionally, manual testing with payloads like id=(SELECT (CASE WHEN (2741=2741) THEN 1 ELSE (SELECT 9394 UNION SELECT 7184) END)) can help confirm the vulnerability. [1]
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 id parameter, minimizing database user permissions by avoiding high-privilege accounts for routine operations, and conducting regular security audits to detect and address vulnerabilities promptly. [1]