Online Shopping SystemApplication · Campcodes

CVE-2025-9692

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-30
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 found in Campcodes Online Shopping System 1.0. Affected is an unknown function of the file /product.php. Performing manipulation of the argument p results in sql injection. The attack may be initiated remotely. The exploit has been made public and could 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

A SQL injection vulnerability exists in Campcodes Online Shopping System 1.0 in the /product.php file. The 'p' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL statements.

MitigationReplace all dynamic SQL queries with parameterized queries or prepared statements. Input validation and escaping should also be implemented for the 'p' parameter.

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
Online Shopping 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 Online Shopping System is installed
    Identify the web application by checking for its characteristic files, pages, or directory structure on the web server. Look for the presence of shopping-related pages or the application root.
    Affected if The application is present on the server and appears to be the Campcodes Online Shopping System
  2. Verify the product version is 1.0
    Check the application version information, which may be in a README file, about page, or configuration files. Compare against the affected version range.
    Affected if The installed version is exactly 1.0
  3. Locate the product.php file
    Search the web server file system for the product.php file in the web root or application directories. This is the file containing the vulnerable code.
    Affected if The product.php file exists in the application directory
  4. Inspect the 'p' parameter handling in product.php
    Open product.php and examine how the 'p' parameter is used in SQL queries. Look for direct insertion of the parameter into SQL statements without sanitization, prepared statements, or parameterized queries.
    Affected if The 'p' parameter is used directly in SQL queries without proper escaping, validation, or parameterized queries
  5. Test the parameter for SQL injection vulnerability
    If accessible, send a crafted request to product.php with the 'p' parameter containing SQL injection payloads (e.g., ' OR '1'='1). Observe whether the application returns unexpected database errors or behaves differently than expected.
    Affected if The application responds with SQL errors or displays unexpected behavior indicating unsanitized input is being executed as SQL

A user is affected if they are running Campcodes Online Shopping System version 1.0 with the product.php file accessible and the 'p' parameter being used in SQL queries without sanitization or prepared statements.

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 all dynamic SQL queries with parameterized queries or prepared statements. Input validation and escaping should also be implemented for the 'p' parameter.

Fix this in Online Shopping System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9692 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