CVE-2025-10831
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 Computer Sales and Inventory System 1.0. Impacted is an unknown function of the file /pages/pro_edit1.php. The manipulation of the argument prodcode leads to sql injection. The attack is possible to be carried out 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 · high confidenceSQL injection vulnerability in Campcodes Computer Sales and Inventory System 1.0 allows remote attackers to inject malicious SQL queries via the prodcode parameter in /pages/pro_edit1.php. The lack of parameterized queries or input sanitization enables attackers to manipulate database queries.
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.
-
Identify installed version of Campcodes Computer Sales and Inventory SystemLocate the application files and check version identifiers in source files, README, or configuration files. Common locations include version.php, about.php, or the root directory documentation.Affected if The installed version is 1.0
-
Verify presence of vulnerable fileCheck if /pages/pro_edit1.php exists in the web root directory of the application.Affected if The file pro_edit1.php exists in the /pages directory
-
Inspect the SQL query implementation in pro_edit1.phpOpen pro_edit1.php in a text editor or via command line and search for SQL queries that use the prodcode parameter without parameterized queries or input sanitization. Look for patterns like $_GET['prodcode'] or $_POST['prodcode'] directly concatenated into SQL strings.Affected if The prodcode parameter is used in SQL queries without prepared statements, parameterization, or input sanitization functions such as mysqli_real_escape_string or htmlspecialchars
-
Determine if the application is accessible over networkCheck if the web server hosting the application is exposed and the /pages/pro_edit1.php endpoint is reachable via HTTP/HTTPS requests.Affected if The vulnerable endpoint is accessible from the network and accepts the prodcode parameter
A user is affected if they are running version 1.0 of Campcodes Computer Sales and Inventory System with the pro_edit1.php file present and the prodcode parameter handled in SQL queries without prepared statements or input sanitization.
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 prepared statements/parameterized queries for all database operations in pro_edit1.php, particularly those using the prodcode parameter. Implement input validation and apply principle of least privilege to the database user.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10831 — 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-10831 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