dbcve.org
Computer Sales And Inventory SystemApplication · Campcodes

CVE-2025-10445

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. Impacted is an unknown function of the file /pages/us_transac.php?action=add. Executing manipulation of the argument Username can lead to sql injection. The attack may be performed from remote. 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 · moderate confidence

SQL injection vulnerability in Campcodes Computer Sales and Inventory System 1.0 allows remote attackers to inject malicious SQL queries through the Username parameter in /pages/us_transac.php?action=add. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially exfiltrating sensitive data, modifying records, or gaining administrative access.

MitigationReplace dynamic SQL query construction with prepared statements/parameterized queries for the Username parameter. Apply input validation and sanitize all user-supplied data before database queries. Apply vendor patch if available.

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. Verify the application is Campcodes Computer Sales and Inventory System
    Locate the application installation directory or check the web server for the presence of files from Campcodes Computer Sales and Inventory System. Look for the application's main directories or files that identify this specific product.
    Affected if The application installed matches Campcodes Computer Sales and Inventory System version 1.0.
  2. Confirm the installed version is 1.0
    Check for version information in the application. This may be in a README file, about page, footer, or configuration file within the application root directory. Compare the version to the affected range.
    Affected if The installed version is exactly 1.0.
  3. Locate the vulnerable script file
    Check if the file /pages/us_transac.php exists in the web application directory. This is the script that handles the transaction functionality and contains the vulnerable code.
    Affected if The file /pages/us_transac.php exists in the installation.
  4. Verify the add action is accessible
    Access the URL endpoint /pages/us_transac.php?action=add in a browser or via curl to confirm the script responds to this action parameter.
    Affected if The endpoint responds and accepts the action parameter.
  5. Inspect the Username parameter handling in the code
    Open /pages/us_transac.php and examine how the Username parameter from the request is used in database queries. Look for direct string concatenation or lack of prepared statements/parameterized queries when constructing SQL statements.
    Affected if The code uses the Username parameter directly in SQL queries without prepared statements or input sanitization.

The environment is affected if Campcodes Computer Sales and Inventory System version 1.0 is installed and the file /pages/us_transac.php handles the Username parameter without prepared statements or input sanitization.

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 query construction with prepared statements/parameterized queries for the Username parameter. Apply input validation and sanitize all user-supplied data before database queries. Apply vendor patch if available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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