CVE-2025-10564
BaseFortify
Publication date: 2025-09-16
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-10564 is a critical SQL injection vulnerability in Campcodes Grocery Sales and Inventory System version 1.0. It exists in the file /ajax.php when the parameter action=delete_category is used. The vulnerability arises because the application does not properly validate or sanitize the user-supplied 'id' parameter, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, modification or deletion of data, and potential control over the affected system. It can also cause service interruptions. Since the attack can be performed remotely without authentication, it poses a significant risk to system confidentiality, integrity, and availability. [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_category endpoint for SQL injection via the 'id' parameter in POST requests. Tools like sqlmap can be used to automate detection. For example, a command using sqlmap could be: sqlmap -u "http://target/ajax.php?action=delete_category" --data="id=1" --risk=3 --level=5 --batch This tests the 'id' parameter for SQL injection vulnerabilities. Additionally, manual testing with boolean-based blind SQL injection payloads such as: id=(SELECT (CASE WHEN (2741=2741) THEN 1 ELSE (SELECT 9394 UNION SELECT 7184) END)) can help confirm the presence of the vulnerability. [2]
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. 2. Apply strict input validation and filtering on the 'id' parameter to ensure it only accepts expected values. 3. Avoid using high-privilege database accounts (like root or admin) for the application. 4. Conduct security audits and patch the vulnerable code promptly. If possible, consider replacing the affected product with a secure alternative until a fix is available. [2, 3]