CVE-2025-10415
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 determined in Campcodes Grocery Sales and Inventory System 1.0. This affects an unknown function of the file /ajax.php?action=save_supplier. 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.
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's /ajax.php file when processing the save_supplier action. The ID parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries through manipulation of this argument.
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 product installationLocate the Campcodes Grocery Sales and Inventory System installation directory. Check for the presence of ajax.php in the web root or application directory.Affected if The system is running Campcodes Grocery Sales and Inventory System and ajax.php exists in the application root.
-
Verify application versionCheck the application version number. This may be in a README file, about page, or version metadata within the source code.Affected if The installed version is 1.0.
-
Locate the affected fileNavigate to the ajax.php file in the application directory and open it for inspection.Affected if The ajax.php file exists and processes the save_supplier action.
-
Examine the save_supplier action handlerWithin ajax.php, search for code handling the 'save_supplier' action. Locate where the ID parameter is processed.Affected if The code contains a case or condition for 'save_supplier' that processes an ID parameter.
-
Check for SQL injection vulnerabilityInspect the code that handles the ID parameter within the save_supplier action. Look for direct insertion of the ID parameter into SQL queries without using prepared statements, parameterized queries, or proper sanitization functions.Affected if The ID parameter is concatenated directly into SQL queries without escaping, binding, or validation.
The environment is affected if running Campcodes Grocery Sales and Inventory System version 1.0 with the ajax.php file present and the save_supplier action handler contains unsanitized ID parameter insertion into 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 dataImmediate remediation requires implementing parameterized queries/prepared statements for all database operations in the affected file and adding proper input validation. Consider restricting network access to the ajax.php endpoint until patched.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10415 — 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-10415 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