CVE-2025-10830
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 Computer Sales and Inventory System 1.0. This issue affects some unknown processing of the file /pages/inv_edit1.php. Executing manipulation of the argument idd can lead to sql injection. The attack can be executed 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 Computer Sales and Inventory System 1.0 allows remote attackers to execute arbitrary SQL commands via manipulation of the 'idd' parameter in /pages/inv_edit1.php.
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 of Campcodes Computer Sales and Inventory SystemLocate and inspect the application's version file, README, or about page. Check the source code headers or configuration files for version strings.Affected if The installed version is 1.0 (exact match)
-
Verify presence of vulnerable scriptCheck if the file /pages/inv_edit1.php exists in the web application directory.Affected if The file /pages/inv_edit1.php is present in the application root or web-accessible directory
-
Check if application handles the idd parameterReview the source code of /pages/inv_edit1.php and locate any code that processes the 'idd' parameter from GET or POST requests.Affected if The 'idd' parameter is directly used in SQL queries without visible sanitization or parameterization in the code
-
Inspect database query construction in inv_edit1.phpOpen /pages/inv_edit1.php and search for SQL query strings (SELECT, UPDATE, DELETE, INSERT) that incorporate the 'idd' variable without prepared statements or escaping functions.Affected if Dynamic SQL queries concatenate or embed the 'idd' parameter directly into database statements
-
Verify web server exposes the affected endpointAttempt to access http://[host]/pages/inv_edit1.php or check web server access logs for requests to this endpoint.Affected if The /pages/inv_edit1.php endpoint is accessible and processes user requests containing the 'idd' parameter
The environment is affected if Campcodes Computer Sales and Inventory System version 1.0 is running and the /pages/inv_edit1.php file processes the 'idd' parameter in unsafe 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 queries with parameterized queries (prepared statements) to prevent SQL injection. Validate and sanitize all user inputs before using them in database queries.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10830 — 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-10830 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