dbcve.org
Sales And Inventory SystemApplication · Campcodes

CVE-2025-7470

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-12
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 Sales and Inventory System 1.0. It has been classified as critical. Affected is an unknown function of the file /pages/product_add.php. The manipulation of the argument image leads to unrestricted upload. It is possible to launch 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 · high confidence

Unrestricted file upload vulnerability in Campcodes Sales and Inventory System 1.0 at /pages/product_add.php. The 'image' parameter lacks proper validation, allowing remote attackers to upload arbitrary files (including malicious PHP scripts) and achieve remote code execution. The CVSS 9.8 indicates trivial exploitability with no authentication required.

MitigationImplement strict allowlist-based file validation for the image upload functionality - validate file extension, MIME type, and file content; store uploads outside web root; disable script execution in upload directories.

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 installed version is 1.0
    Locate the application source code and check version.php, README, or any version indicator file. Alternatively, access the login page and view page source for version strings, or check HTTP headers/Server tokens if exposed.
    Affected if The installed version is exactly 1.0 of Campcodes Sales and Inventory System.
  2. Verify vulnerable file exists
    Check if /pages/product_add.php exists in the web root or application directory. This can be done via file system inspection or by attempting to access the URL directly (e.g., GET to http://target/pages/product_add.php).
    Affected if The file /pages/product_add.php is present in the deployed application.
  3. Confirm image upload functionality is accessible
    Locate the product addition form in the application (typically under a 'Products' or 'Add Product' menu item). Check if the form includes an 'image' file input field and submits to product_add.php.
    Affected if The product_add.php script accepts file uploads via an 'image' parameter and is accessible without proper restrictions.
  4. Check if uploads directory allows script execution
    Inspect the uploads directory configuration. Check if .htaccess or web server config disables script execution in the uploads folder. Look for uploaded test files being executable as PHP.
    Affected if Uploaded files can be executed as scripts (e.g., .php files run instead of being served as static content).
  5. Test upload functionality with non-image file
    Submit a POST request to product_add.php with a .php file uploaded via the 'image' parameter (requires authentication if the endpoint is protected). Check if the file is accepted and stored.
    Affected if The application accepts and stores files with dangerous extensions (e.g., .php, .phtml) without validating the file type.

If running version 1.0 with the product_add.php endpoint accessible and no restrictions on uploaded file types or execution, the environment is vulnerable to CVE-2025-7470.

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

Implement strict allowlist-based file validation for the image upload functionality - validate file extension, MIME type, and file content; store uploads outside web root; disable script execution in upload directories.

Fix this in Sales And Inventory System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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