dbcve.org
B2b2c Multi BusinessApplication · Niushop

CVE-2024-0933

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-26
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
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 Niushop B2B2C V5 and classified as critical. Affected by this issue is some unknown functionality of the file \app\model\Upload.php. The manipulation leads to unrestricted upload. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-252140. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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 critical unrestricted file upload vulnerability exists in Niushop B2B2C V5's \app\model\Upload.php, allowing remote attackers to upload arbitrary files including executable scripts without proper validation. This can lead to remote code execution (RCE) on the server. The vulnerability has been publicly disclosed with working exploit code.

MitigationImplement strict file upload validation including allowlist-based extension checking, MIME type verification, file content magic byte inspection, and storing uploads outside webroot or with executable permissions removed. Consider disabling the upload functionality until a vendor patch is available.

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
B2b2c Multi BusinessApplication
Affected:= 5.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 Niushop B2B2C V5 installation
    Locate the application by searching for the 'niushop' directory or checking your web server document root for the presence of the Niushop application files, particularly the \app\model\Upload.php file mentioned in the CVE.
    Affected if The Niushop B2B2C V5 application is present on the server.
  2. Identify the installed version
    Check the application version by looking for a version file in the application root directory, the admin panel about page, or a config file that contains the version string. Compare your version to 5.0.
    Affected if The installed version is exactly 5.0.
  3. Locate the vulnerable Upload.php file
    Navigate to \app\model\Upload.php in your Niushop installation directory and inspect the file. Look for functions that handle file uploads, specifically any upload or save functions that lack extension or MIME type validation.
    Affected if The file exists and contains upload handling code without proper validation checks.
  4. Identify accessible upload directories
    Check the runtime, upload, or public upload directories within the Niushop installation for any web-accessible folders where uploaded files are stored.
    Affected if Upload directories are accessible via web and allow execution of uploaded files.
  5. Scan for suspicious uploaded files
    List all files in the upload directories and check for unexpected file types such as .php, .phtml, .jpg.php, or other executable extensions. Also check for recently created files with unusual names.
    Affected if Unexpected PHP scripts or other executable files exist in upload directories.
  6. Review web server access logs
    Examine web server access logs for POST requests to the upload endpoint, particularly those containing unusual file extensions or double extensions like .php.jpg that may indicate exploitation attempts.
    Affected if Log entries show uploads of executable file types to the application.

You are affected if Niushop B2B2C version 5.0 is installed and the upload functionality is exposed without proper file validation controls in place.

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 file upload validation including allowlist-based extension checking, MIME type verification, file content magic byte inspection, and storing uploads outside webroot or with executable permissions removed. Consider disabling the upload functionality until a vendor patch is available.

Fix this in B2b2c Multi Business Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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