CVE-2025-10563
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 has been found in Campcodes Grocery Sales and Inventory System 1.0. This impacts an unknown function of the file /ajax.php?action=save_category. Such manipulation of the argument ID leads to sql injection. The attack can be executed remotely. The exploit has been disclosed to the public 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 · moderate confidenceA critical SQL injection vulnerability exists in Campcodes Grocery Sales and Inventory System 1.0 in the /ajax.php?action=save_category endpoint. The ID parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL commands. The CVSS 9.8 score indicates trivial exploitability with potentially complete confidentiality and integrity impact.
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.
-
Verify the application versionLocate the version identifier in the application source code, typically found in a README file, about page, or version constant within PHP files. Compare this version to 1.0.Affected if The installed version is 1.0 of Campcodes Grocery Sales and Inventory System.
-
Confirm the vulnerable endpoint existsCheck if the file ajax.php exists in the web root directory of the application and is accessible via HTTP.Affected if The ajax.php file exists and is reachable via the web server.
-
Identify the save_category functionSearch the ajax.php file for the save_category case or function definition. Verify that it handles an ID parameter.Affected if The save_category function or case handler is present in ajax.php and processes an ID parameter.
-
Inspect SQL query handling in save_categoryExamine the save_category code to locate SQL queries. Look for direct concatenation or interpolation of the ID parameter into SQL statements without prepared statements or escaping functions.Affected if The ID parameter is used directly in SQL queries without parameterized binding or input sanitization.
-
Check application accessibilityDetermine if the web application is actively running and reachable over the network.Affected if The application is deployed and the ajax.php endpoint is accessible from the network.
A user is affected if they are running version 1.0 of Campcodes Grocery Sales and Inventory System with the ajax.php endpoint accessible and the save_category function vulnerable to SQL injection through the ID parameter.
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 dataImmediately implement prepared statements/parameterized queries for the ID parameter in the save_category function. If possible, disable the affected endpoint until a patch is applied. Conduct a full code audit for additional SQL injection vulnerabilities.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10563 — 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-10563 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