CVE-2024-0352
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 classified as critical was found in Likeshop up to 2.5.7.20210311. This vulnerability affects the function FileServer::userFormImage of the file server/application/api/controller/File.php of the component HTTP POST Request Handler. The manipulation of the argument file leads to unrestricted upload. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-250120.
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 Likeshop's File.php controller (userFormImage function). The HTTP POST file upload handler fails to validate file types, allowing remote attackers to upload malicious executables (PHP shells, web shells) to the server, potentially achieving remote code execution.
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<= 2.5.7.20210311CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Likeshop is installedCheck your web server for the presence of Likeshop application files. Common locations include /var/www/html/, /home/*/public_html/, or your web root directory. Look for directories containing 'likeshop' or application files with likeshop references.Affected if Likeshop is present on the server
-
Verify the Likeshop versionLocate the version file or bootstrap file in the Likeshop installation directory. Common paths include a version.php, composer.json, or config file that displays the application version. Compare your version to <= 2.5.7.20210311.Affected if Installed version is 2.5.7.20210311 or earlier
-
Locate the vulnerable File.php controllerSearch for the file 'File.php' in the application source code, typically under application/controller/ or app/Http/Controllers/. Verify it contains the 'userFormImage' function.Affected if File.php with userFormImage function exists in the application
-
Check if upload functionality is accessibleExamine your web server routing or URL patterns to determine if the userFormImage endpoint is exposed. This is typically accessible via an HTTP POST to an upload-related route.Affected if The upload endpoint is routable and accepts POST requests
-
Inspect the upload directoryCheck the configured upload directory in the application (commonly /uploads/, /public/uploads/, or similar). Determine if files stored there can be executed as scripts (PHP, .exe, .sh).Affected if Upload directory exists within the web root and allows script execution
You are affected if Likeshop version 2.5.7.20210311 or earlier is installed, the File.php controller with userFormImage function exists, and the upload functionality is accessible without file type restrictions.
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 dataImmediately restrict upload functionality to whitelist safe file types (images, documents); implement server-side MIME type and content validation; store uploads outside web root or disable script execution in upload directories; apply vendor patches when available.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0352 — 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-0352 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