dbcve.org
Sales And Inventory SystemApplication · Campcodes

CVE-2025-6311

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-20
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, which was classified as critical, was found in Campcodes Sales and Inventory System 1.0. This affects an unknown part of the file /pages/account_add.php. The manipulation of the argument id/amount leads to sql injection. It is possible to initiate the attack 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 · moderate confidence

SQL injection vulnerability in Campcodes Sales and Inventory System 1.0 at /pages/account_add.php. The id and amount parameters are not properly sanitized, allowing attackers to inject malicious SQL queries remotely.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation on the id and amount parameters.

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
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 Campcodes Sales and Inventory System installation
    Locate the application web root directory and verify the presence of the Campcodes Sales and Inventory System files, typically found in the web server document root. Look for the main application directory containing the source code.
    Affected if The application is present on the system
  2. Verify the exact version number
    Check the application version by examining version files, about pages, or metadata within the application source code. Compare the installed version against the affected version 1.0.
    Affected if The installed version is exactly 1.0
  3. Check for the vulnerable script
    Verify that the file /pages/account_add.php exists within the application web root. This is the specific file containing the SQL injection vulnerability.
    Affected if The file /pages/account_add.php exists in the installation
  4. Confirm application is network accessible
    Determine if the application is accessible over the network by checking the web server configuration and confirming the application responds to HTTP/HTTPS requests.
    Affected if The application is accessible via network and the vulnerable endpoint can be reached
  5. Identify database configuration
    Examine the database configuration file within the application to confirm which database backend is in use and whether it contains user-supplied data that could be targeted.
    Affected if The application uses a database that processes user input through the vulnerable parameters

A system is affected if it runs Campcodes Sales and Inventory System version 1.0 with the file /pages/account_add.php accessible over the network, as the id and amount parameters in that script are vulnerable to SQL injection.

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

Replace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation on the id and amount parameters.

Recommended fix Moderate confidence
  1. 1. Locate the vulnerable file /pages/account_add.php in the application installation
  2. 2. Identify the SQL query that uses the 'id' and/or 'amount' parameters without proper sanitization
  3. 3. Replace dynamic SQL queries with prepared statements (parameterized queries) using PDO or mysqli
  4. 4. For each user-supplied input (id, amount), bind parameters instead of concatenating strings into the SQL query
  5. 5. Example fix: Change 'SELECT * FROM accounts WHERE id='.$id to '$stmt = $pdo->prepare("SELECT * FROM accounts WHERE id = ?"); $stmt->execute([$id]);'
  6. 6. Apply the same parameterized query pattern to any other SQL statements in the file that accept user input
  7. 7. Validate that the application still functions correctly after the code changes
  8. 8. Test the application with SQL injection payloads in the id and amount parameters to confirm the vulnerability is remediated

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

Fix this in Sales And Inventory System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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