CVE-2025-10563
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-10563 is a critical SQL injection vulnerability in Campcodes Grocery Sales and Inventory System version 1.0. It occurs in the file /ajax.php when the action parameter is set to save_category. The vulnerability arises because the id parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, including data leakage, modification, deletion, and potentially full system control. The attack can be executed remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to remotely execute arbitrary SQL commands on your database without any authentication. This can lead to unauthorized data access, data leakage of sensitive information, data modification or deletion, disruption of services, and potentially full control over the affected system. Because the exploit is publicly available and easy to execute, the risk is high. [1, 2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can negatively affect compliance with standards such as GDPR and HIPAA because it risks unauthorized access and exposure of sensitive personal or health data. SQL injection attacks can lead to data breaches, violating confidentiality and integrity requirements mandated by these regulations. Organizations using the affected system may fail to protect personal data adequately, resulting in non-compliance and potential legal and financial consequences. [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=save_category endpoint for SQL injection on the 'id' parameter. Tools like sqlmap can automate detection and exploitation. Example payloads include boolean-based blind SQL injection such as setting 'id' to `(SELECT (CASE WHEN (6157=6157) THEN 2 ELSE (SELECT 5232 UNION SELECT 6449) END))` or time-based blind SQL injection like `2 AND (SELECT 7658 FROM (SELECT(SLEEP(5)))VHsu)`. Using sqlmap with the target URL and specifying the vulnerable parameter can confirm the presence of the vulnerability. [3]
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. Since no known countermeasures or patches are available, replacing the affected product with an alternative solution is also suggested to secure the system and maintain data integrity. [2, 3, 1]