CVE-2025-10786
BaseFortify
Publication date: 2025-09-22
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-10786 is a critical SQL injection vulnerability in Campcodes Grocery Sales and Inventory System version 1.0. It exists in the /ajax.php?action=delete_user endpoint due to improper validation and sanitization of the 'id' parameter. This flaw allows attackers to inject malicious SQL queries remotely without authentication, enabling unauthorized access to the database. Attackers can manipulate, delete, or expose sensitive data by exploiting this vulnerability. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, deletion of data, and potential full system control. It can also cause service disruption. Since no authentication is required, attackers can remotely exploit this flaw easily, compromising the confidentiality, integrity, and availability of the system and its data. [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?action=delete_user endpoint for SQL injection via the 'id' parameter. Using tools like sqlmap to send crafted payloads can confirm the presence of the flaw. For example, a command such as `sqlmap -u "http://target/ajax.php?action=delete_user" --data="id=1" --risk=3 --level=5` can be used to test for SQL injection. Additionally, manual testing with payloads like `id=(SELECT (CASE WHEN (2741=2741) THEN 1 ELSE (SELECT 9394 UNION SELECT 7184) END))` in POST requests can help detect boolean-based blind SQL injection. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Applying strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) Conducting regular security audits to detect and fix vulnerabilities promptly. If possible, consider replacing the affected product with a secure alternative. [2, 3]