CVE-2025-10786
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA flaw has been found in Campcodes Grocery Sales and Inventory System 1.0. This vulnerability affects unknown code of the file /ajax.php?action=delete_user. This manipulation of the argument ID causes sql injection. The attack can be initiated remotely. The exploit has been published and may be used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in Campcodes Grocery Sales and Inventory System 1.0 allows remote attackers to inject arbitrary SQL commands via the ID parameter in the /ajax.php?action=delete_user endpoint. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially allowing data exfiltration, modification, or complete system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm the application identityCheck the application name by inspecting the web application banner, title, or source code. Look for 'Campcodes Grocery Sales and Inventory System' in the HTML title tag, footer, or branding elements.Affected if The application is Campcodes Grocery Sales and Inventory System
-
Verify the installed versionInspect application files or configuration for the version number. Check files like README, version.php, or any about/info page. Compare against the affected version 1.0.Affected if The installed version is 1.0
-
Check for the vulnerable ajax.php fileLocate the ajax.php file in the web root directory. Verify its existence and accessibility at the path /ajax.php.Affected if The file ajax.php exists in the web application root
-
Confirm delete_user endpoint availabilityTest access to /ajax.php?action=delete_user by sending a request (even with a benign ID value) to confirm the endpoint responds.Affected if The delete_user action endpoint is accessible and responds to requests
-
Inspect ID parameter handling in delete_userExamine the source code of ajax.php, specifically the delete_user case. Look for direct use of the ID parameter in SQL queries without parameterized queries or input sanitization.Affected if The ID parameter is used directly in SQL queries without prepared statements or proper escaping
Your environment is affected if you are running Campcodes Grocery Sales and Inventory System version 1.0 with the ajax.php file containing the delete_user functionality that uses the ID parameter unsafely in SQL queries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL construction with parameterized queries or prepared statements in the delete_user action of ajax.php, and implement strict input validation on the ID parameter. Additionally, apply the principle of least privilege to the database account used by the application.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10786 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10786 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data