dbcve.org
SparkshopApplication

CVE-2024-40425

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-16
Fix available
A fix is available. Upgrade to 1.1.7 or later.
See remediation →
100/100
Remediation priority · Urgent
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
File Upload vulnerability in Nanjin Xingyuantu Technology Co Sparkshop (Spark Mall B2C Mall v.1.1.6 and before allows a remote attacker to execute arbitrary code via the contorller/common.php component.

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

File upload vulnerability in the controller/common.php component of Sparkshop (Spark Mall B2C Mall) versions 1.1.6 and earlier allows remote unauthenticated attackers to upload malicious files, achieving arbitrary code execution on the affected system.

MitigationUpgrade to a version beyond v.1.1.6 if available; otherwise, implement strict allowlist-based file validation (MIME type, extension, file content), store uploads outside the web root, disable script execution in upload directories, and rename uploaded files to prevent direct access.

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
SparkshopApplication
Affected:< 1.1.7

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. Check Sparkshop version
    Locate the version file or check the admin dashboard for the installed version number. Common locations include a version.php file in the root or app directory, or displayed in the admin panel footer.
    Affected if Installed version is 1.1.6 or earlier (anything below 1.1.7)
  2. Verify controller/common.php exists
    Locate and inspect the controller/common.php file in the Sparkshop installation directory. Check if the file contains upload handling functions (look for file upload-related code, move_uploaded_file, or similar functions).
    Affected if The controller/common.php file exists and contains file upload handling logic
  3. Identify public upload endpoints
    Review application routing configuration to identify routes that invoke the common.php controller. Check for accessible URLs that process file uploads without requiring authentication.
    Affected if There is a publicly accessible endpoint that routes to the vulnerable upload functionality in common.php
  4. Check upload directory configuration
    Examine the configuration for upload directories - verify if uploaded files are stored inside the web root and if script execution is permitted in those directories.
    Affected if Uploaded files are stored within the web-accessible directory and execution of scripts is allowed

You are affected if Sparkshop version is 1.1.6 or earlier AND the upload functionality in controller/common.php is exposed to unauthenticated users.

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
Upgrade available Upgrade to 1.1.7 or later
Fixed in 1.1.7
Interim mitigation

Upgrade to a version beyond v.1.1.6 if available; otherwise, implement strict allowlist-based file validation (MIME type, extension, file content), store uploads outside the web root, disable script execution in upload directories, and rename uploaded files to prevent direct access.

Recommended fix Moderate confidence

1.1.7

  1. 1. Backup your current Sparkshop installation including all files and database
  2. 2. Download Sparkshop version 1.1.7 or later from the official source
  3. 3. Replace the existing installation files with the new version, preserving your configuration and upload directories
  4. 4. Verify that controller/common.php has been updated to include proper file upload validation
  5. 5. Test the application functionality to ensure the upgrade was successful
  6. 6. Monitor logs for any suspicious upload attempts

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

Fix this in Sparkshop Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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