dbcve.org
Computer Sales And Inventory SystemApplication · Campcodes

CVE-2025-10436

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-15
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 weakness has been identified in Campcodes Computer Sales and Inventory System 1.0. The impacted element is an unknown function of the file /pages/sup_searchfrm.php?action=edit. This manipulation of the argument ID causes sql injection. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be exploited.

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

A SQL injection vulnerability exists in Campcodes Computer Sales and Inventory System 1.0 in the /pages/sup_searchfrm.php?action=edit endpoint. The ID parameter is not properly sanitized before being used in SQL queries, allowing an attacker to inject malicious SQL statements. This can lead to unauthorized database access, data exfiltration, or potential command execution in some configurations.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation on all user-supplied parameters. If immediate patching is not possible, consider deploying a WAF rule to filter SQL injection payloads.

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 Campcodes Computer Sales and Inventory System
    Look for application files or headers identifying this product. Check for the presence of /pages/ directory structure typical to this system.
    Affected if The system is Campcodes Computer Sales and Inventory System version 1.0
  2. Verify the vulnerable file sup_searchfrm.php exists
    Check if the file /pages/sup_searchfrm.php exists in the web root or application directory.
    Affected if The file sup_searchfrm.php exists in the pages directory
  3. Check the installed version
    Look for version indicators such as version files, footer/header files with version info, or admin panel about section showing version 1.0.
    Affected if The installed version is exactly 1.0 (the only affected version)
  4. Determine if the edit action endpoint is accessible
    Attempt to access or check routing configuration for /pages/sup_searchfrm.php?action=edit to see if the endpoint accepts requests.
    Affected if The sup_searchfrm.php endpoint with action=edit is accessible and processes the ID parameter
  5. Check if ID parameter is processed without prepared statements
    Review the source code of sup_searchfrm.php if accessible, looking for direct use of $_GET['ID'] or similar in SQL queries without prepared statements or sanitization functions.
    Affected if The code shows the ID parameter is used directly in SQL queries without parameter binding or input validation

You are affected if you are running Campcodes Computer Sales and Inventory System version 1.0 and the /pages/sup_searchfrm.php endpoint with the action=edit parameter is accessible and processes the ID parameter without SQL parameterization.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation on all user-supplied parameters. If immediate patching is not possible, consider deploying a WAF rule to filter SQL injection payloads.

Fix this in Computer Sales And Inventory System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10436 — 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-10436 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