CVE-2024-3804
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, which was classified as critical, has been found in Vesystem Cloud Desktop up to 20240408. This issue affects some unknown processing of the file /Public/webuploader/0.1.5/server/fileupload2.php. 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 identifier VDB-260777 was assigned to this vulnerability. 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 · moderate confidenceUnrestricted file upload vulnerability in Vesystem Cloud Desktop's /Public/webuploader/0.1.5/server/fileupload2.php. The 'file' argument can be manipulated to upload arbitrary files without proper validation, potentially allowing remote code execution.
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.
-
Confirm Vesystem Cloud Desktop installationLocate the Vesystem Cloud Desktop installation directory on the server, typically found under the web root (e.g., /var/www/html, C:\inetpub\wwwroot, or similar). Look for the main application directories.Affected if The application is not found or is installed in a non-standard location that doesn't follow the web root structure.
-
Verify vulnerable file existsCheck for the presence of /Public/webuploader/0.1.5/server/fileupload2.php within the Vesystem installation directory. Use file system search or command: find /path/to/webroot -name 'fileupload2.php' -path '*/webuploader/0.1.5/*'Affected if The file fileupload2.php exists in the webuploader/0.1.5/server subdirectory.
-
Confirm web server serves the upload endpointTest network access to the /Public/webuploader/0.1.5/server/fileupload2.php endpoint by attempting an HTTP request (e.g., curl http://TARGET/Public/webuploader/0.1.5/server/fileupload2.php)Affected if The endpoint returns an HTTP response (200, 400, 405, or similar) indicating it is accessible via HTTP.
-
Check if endpoint requires authenticationReview web server configuration (Apache .htaccess, Nginx config, or application-level auth) and test the upload endpoint without credentials to determine if authentication is enforced.Affected if The upload endpoint accepts requests without requiring valid authentication credentials.
If Vesystem Cloud Desktop is installed, the vulnerable fileupload2.php exists in the webuploader/0.1.5 directory, and the upload endpoint is accessible without proper authentication, the environment is affected by CVE-2024-3804.
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 dataDisable or restrict access to the vulnerable upload endpoint. Implement strict file type validation, whitelist allowed extensions, and store uploads outside web root. Consider WAF rules to block malicious file uploads.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3804 — 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-3804 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