CVE-2025-10564
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 vulnerability was found in Campcodes Grocery Sales and Inventory System 1.0. Affected is an unknown function of the file /ajax.php?action=delete_category. Performing manipulation of the argument ID results in sql injection. The attack is possible to be carried out remotely. The exploit has been made public and could 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 · moderate confidenceSQL injection vulnerability in Campcodes Grocery Sales and Inventory System 1.0 allows remote unauthenticated attackers to inject malicious SQL queries through the ID parameter in the /ajax.php?action=delete_category endpoint.
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 installed version is 1.0Locate the application files and check for version indicators such as a version.php file, README, or footer/version string within the web application. Compare against the affected version range.Affected if The installed version is exactly 1.0 (the only affected version).
-
Identify ajax.php locationFind the ajax.php file within the web application directory structure. This is typically in the root or an includes folder of the Campcodes Grocery Sales and Inventory System.Affected if The file ajax.php exists in the application, indicating the vulnerable endpoint is present.
-
Check if delete_category function existsOpen ajax.php and search for the string 'delete_category' within the code. This function handles the vulnerable SQL query.Affected if The delete_category function is defined in ajax.php, meaning the vulnerable code path exists.
-
Verify endpoint is accessibleAttempt to access the URL pattern /ajax.php?action=delete_category on the server. This can be done via HTTP request or by checking web server access logs for requests to this endpoint.Affected if The endpoint responds to requests, indicating it is exposed and reachable.
-
Inspect the SQL query in delete_categoryExamine the delete_category function code in ajax.php to confirm it uses dynamic SQL concatenation with the ID parameter rather than parameterized queries.Affected if The ID parameter is directly concatenated into the SQL query without using prepared statements or parameter binding.
The system is affected if it is running version 1.0 of Campcodes Grocery Sales and Inventory System and the delete_category endpoint in ajax.php uses dynamic SQL with the ID parameter without parameterized 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 queries with parameterized queries/prepared statements in the delete_category function, and audit all other ajax.php endpoints for similar injection vulnerabilities. Apply principle of least privilege to the database user.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10564 — 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-10564 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