CVE Alert: CVE-2025-10565 – Campcodes – Grocery Sales and Inventory System

CVE-2025-10565

HIGHNo exploitation known

A vulnerability was determined in Campcodes Grocery Sales and Inventory System 1.0. Affected by this vulnerability is an unknown functionality of the file /ajax.php?action=delete_receiving. Executing manipulation of the argument ID can lead to sql injection. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized.

CVSS v3.1 (7.3)
Vendor
Campcodes
Product
Grocery Sales and Inventory System
Versions
1.0
CWE
CWE-89, SQL Injection
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Published
2025-09-16T20:32:09.802Z
Updated
2025-09-16T20:32:09.802Z

AI Summary Analysis

Risk verdict

High risk due to remote, unauthenticated SQL injection with a publicly disclosed exploit affecting a network-facing endpoint.

Why this matters

The flaw can enable data disclosure and tampering in the backend. For a grocery sales and inventory system, that could compromise stock integrity, order data, and customer information, leading to financial loss and reputational damage.

Most likely attack path

An attacker can directly target the network-facing AJAX endpoint and supply crafted ID values to trigger the SQL injection. No authentication or user interaction is required, so automated exploitation is plausible; public disclosure increases likelihood of use, with impact tied to the database that the application communicates with.

Who is most exposed

deployments that expose the web interface to the internet—common for on-premises or hosted setups used by small to midsize retailers—are at greatest risk.

Detection ideas

  • SQL errors or abnormal responses from the vulnerable endpoint in app logs.
  • Bursts of requests with varied or unusual IDs to delete_receiving.
  • Anomalous DB queries: long-running or unexpected data access patterns.
  • IDS/IPS alerts for SQL injection patterns targeting this endpoint.
  • Unexplained stock or order data changes following access attempts.

Mitigation and prioritisation

  • Apply the vendor patch or upgrade to the fixed version.
  • Enforce parameterised queries, input validation, and ensure ID is strictly numeric.
  • Restrict or disable the vulnerable endpoint; require authentication and CSRF protection.
  • Apply least-privilege database accounts and network segmentation.
  • Enhance logging, detection, and perform staged testing before production deployment.
  • If KEV true or EPSS ≥ 0.5, treat as priority 1; otherwise, prioritise as high.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.