dbcve.org
Shudong ShareApplication · Hfo4

CVE-2024-8338

HIGH · 8.8 CVSS v3.1 Published 2024-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 →
94/100
Remediation priority · Urgent
Remotely reachable 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 HFO4 shudong-share 2.4.7. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /includes/fileReceive.php of the component File Extension Handler. The manipulation of the argument file leads to unrestricted upload. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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 HFO4 shudong-share 2.4.7 in /includes/fileReceive.php. The file extension handler does not properly validate the 'file' argument, allowing remote attackers to upload arbitrary files including executable code. Public exploit available.

MitigationSince the product is no longer supported, implement custom file upload validation: whitelist allowed extensions, verify MIME types, rename uploaded files, store outside webroot, and 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
Shudong ShareApplication
Affected:= 2.4.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 installed shudong-share version
    Locate the version file (commonly version.php, README, or footer metadata) or check the admin panel for version information. Compare against version 2.4.7.
    Affected if Running shudong-share version 2.4.7 exactly
  2. Verify fileReceive.php exists
    Inspect the /includes/fileReceive.php file on the web server. Confirm the file exists in the installation.
    Affected if The file /includes/fileReceive.php exists and is accessible via web
  3. Confirm file upload feature is enabled
    Check if the upload functionality is active in the application settings or if the upload endpoint responds to requests.
    Affected if File upload functionality is enabled and accessible to users
  4. Review extension validation in fileReceive.php
    Open /includes/fileReceive.php and examine the file extension validation logic for the 'file' parameter. Look for whitelist or blacklist validation routines.
    Affected if No proper file extension whitelist validation exists or validation can be bypassed
  5. Check upload directory configuration
    Identify where uploaded files are stored. Determine if the directory is web-accessible and if script execution is restricted.
    Affected if Upload directory is web-accessible and script execution is not disabled

You are affected if running shudong-share version 2.4.7 with the /includes/fileReceive.php endpoint accessible and file upload enabled without proper extension validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the product is no longer supported, implement custom file upload validation: whitelist allowed extensions, verify MIME types, rename uploaded files, store outside webroot, and disable script execution in upload directories.

Recommended fix High confidence
  1. This vulnerability affects Shudong Share version 2.4.7, which is explicitly noted as a product no longer supported by the maintainer.
  2. No patch, fix, or upgrade path is available from the vendor for this version.
  3. Consider migrating to an actively maintained file sharing solution or alternative platform.
  4. If continued use is mandatory, implement strict compensating controls: restrict network access to the fileReceive.php endpoint, deploy web application firewall rules to block executable file uploads, and implement external file upload validation at the server level.
Caveat Product is end-of-life and unsupported; no upgrade path available

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

Fix this in Shudong Share Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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