CVE-2025-10031
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 security vulnerability has been detected in Campcodes Grocery Sales and Inventory System 1.0. Impacted is an unknown function of the file /ajax.php?action=delete_sales. The manipulation of the argument ID leads to sql injection. Remote exploitation of the attack is possible. The exploit has been disclosed publicly 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 execute arbitrary SQL commands via the ID parameter in /ajax.php?action=delete_sales. The lack of input sanitization or parameterized queries in this endpoint enables complete database 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 product and versionInspect your web application files, typically in the root directory, for a file containing version information (such as readme.txt, about.php, or a config file). Also check the page source of any accessible login or main page for 'Grocery Sales and Inventory System' and version '1.0'.Affected if The installed application is Campcodes Grocery Sales And Inventory System version 1.0
-
Locate the vulnerable endpointCheck if the file /ajax.php exists in your web server document root. This file is typically found in the main application directory accessible via HTTP/HTTPS.Affected if The ajax.php file exists in the web-accessible directory
-
Verify delete_sales action handlingExamine the ajax.php source code (if accessible via file system or if you have source code access) and search for a case or condition handling 'delete_sales'. If you cannot view source, attempt to access the URL pattern /ajax.php?action=delete_sales with a test ID parameter.Affected if The ajax.php file contains a handler for the delete_sales action and accepts the ID parameter via GET request
-
Check for input sanitizationIf you have access to the source code, inspect the delete_sales function in ajax.php to see if the ID parameter is passed directly into an SQL query without sanitization or prepared statements. Look for signs of mysql_query, mysqli_query, or PDO query execution where the ID is concatenated rather than bound as a parameter.Affected if The ID parameter from the URL is used directly in an SQL query without sanitization, escaping, or parameterized binding
-
Assess network exposureDetermine if the web application is accessible from untrusted networks. Check your web server configuration (Apache/Nginx/IIS) to see if ajax.php is exposed to the public internet or only accessible internally.Affected if The /ajax.php endpoint is publicly accessible over the internet without authentication or IP restriction
You are affected if you are running Campcodes Grocery Sales And Inventory System version 1.0 and the ajax.php file with the delete_sales action is accessible and uses unsanitized SQL queries for 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 remediate by replacing dynamic SQL queries with parameterized queries/prepared statements in the delete_sales function. Conduct a comprehensive code audit of the entire application to identify and fix similar SQL injection vulnerabilities across all endpoints.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10031 — 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-10031 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