CVE-2024-6730
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 · uneditedA vulnerability was found in Nanjing Xingyuantu Technology SparkShop up to 1.1.6. It has been rated as critical. This issue affects some unknown processing of the file /api/Common/uploadFile. The manipulation of the argument file leads to unrestricted upload. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-271403.
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 confidenceUnrestricted file upload vulnerability in the /api/Common/uploadFile endpoint of SparkShop e-commerce software up to version 1.1.6. The lack of proper validation on the 'file' argument allows attackers to upload arbitrary files, potentially leading to remote code execution if executable files are placed in web-accessible locations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify SparkShop installationLocate the SparkShop installation directory and check for composer.json, package.json, or other project identification files that confirm the application is SparkShop.Affected if The application is confirmed to be SparkShop e-commerce software.
-
Determine installed versionCheck the version file (such as version.php, composer.json, or a dedicated version config) to identify the exact version number installed.Affected if The installed version is 1.1.6 or any version lower than 1.1.6.
-
Verify upload endpoint existsInspect the application source code for the /api/Common/uploadFile endpoint or route handler. This is typically found in the routes/api.php file or in a Common controller handling file uploads.Affected if The /api/Common/uploadFile endpoint exists and is accessible without authentication.
-
Check file type validationExamine the uploadFile endpoint handler code to see if there is any extension, MIME type, or magic byte validation on the 'file' parameter.Affected if No allowlist-based file type validation is present, or validation can be easily bypassed.
-
Verify upload storage locationCheck the application configuration to determine where uploaded files are stored. Inspect the web server configuration to confirm if that storage directory is web-accessible.Affected if Uploaded files are stored in a directory accessible via HTTP/HTTPS and script execution is not disabled.
A user is affected if they are running SparkShop version 1.1.6 or lower AND the /api/Common/uploadFile endpoint is accessible without proper file type validation AND uploaded files are stored in a web-accessible location.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict allowlist-based file type validation (extension and MIME type), verify file content using magic bytes, store uploads outside webroot, disable script execution in upload directories, and apply vendor patch when available.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6730 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6730 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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