dbcve.org
Computer Sales And Inventory SystemApplication · Campcodes

CVE-2025-11109

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was identified in Campcodes Computer Sales and Inventory System 1.0. The affected element is an unknown function of the file /pages/us_edit.php?action=edit. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The exploit is publicly available and might 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 confidence

SQL injection vulnerability in Campcodes Computer Sales and Inventory System 1.0 at /pages/us_edit.php?action=edit. The 'ID' parameter is not properly sanitized, allowing attackers to inject malicious SQL queries. The vulnerability is remotely exploitable and public exploits exist.

MitigationImplement parameterized queries or prepared statements for all database operations, particularly the ID parameter in us_edit.php. Apply input validation and escape user-supplied data before 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
Computer Sales And Inventory SystemApplication
Affected:= 1.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the application is installed
    Locate the Campcodes Computer Sales and Inventory System installation directory or running instance. Check for files such as us_edit.php within the /pages directory.
    Affected if The Campcodes Computer Sales and Inventory System is present in the environment.
  2. Identify the installed version
    Search for version information in the application source files, README, or configuration files. Check the main index page or about section for version details.
    Affected if The installed version is 1.0.
  3. Verify the vulnerable file exists
    Check if the file /pages/us_edit.php exists in the web application directory.
    Affected if The file us_edit.php exists in the /pages directory.
  4. Inspect the ID parameter handling
    Open /pages/us_edit.php and examine how the 'ID' parameter from the query string is used in database queries. Look for direct concatenation of the ID parameter into SQL statements without sanitization or parameterized queries.
    Affected if The ID parameter is used in SQL queries without prepared statements or input sanitization.

If the Campcodes Computer Sales and Inventory System version 1.0 is installed and the /pages/us_edit.php file contains unsanitized ID parameter usage in SQL queries, the environment is affected by CVE-2025-11109.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements for all database operations, particularly the ID parameter in us_edit.php. Apply input validation and escape user-supplied data before database queries.

Recommended fix Moderate confidence
  1. 1. Locate the vulnerable file /pages/us_edit.php on the affected server
  2. 2. Identify the SQL query that uses the 'ID' parameter from the $_GET['ID'] or similar superglobal
  3. 3. Replace any string concatenation or interpolation of the ID parameter in SQL queries with prepared statements/parameterized queries
  4. 4. For example, change `$sql = "SELECT * FROM users WHERE ID = " . $_GET['ID'];` to use `$stmt = $pdo->prepare('SELECT * FROM users WHERE ID = :id'); $stmt->execute(['id' => $_GET['ID']]);`
  5. 5. If using mysqli, change to `$stmt = $mysqli->prepare('SELECT * FROM users WHERE ID = ?'); $stmt->bind_param('i', $_GET['ID']);`
  6. 6. After applying the patch, restart any web server services
  7. 7. Test the patched endpoint /pages/us_edit.php?action=edit with both valid and malicious ID values to confirm the injection is blocked
  8. 8. If possible, deploy a WAF (Web Application Firewall) rule as an additional layer of defense until the patch is fully verified

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Computer Sales And Inventory System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11109 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11109 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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