Unrestricted File UploadWeakness · CWE-434

CVE-2024-3803

MEDIUM · 6.3 CVSS v3.1 Published 2024-04-15

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

69/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

A vulnerability classified as critical was found in Vesystem Cloud Desktop up to 20240408. This vulnerability affects unknown code of the file /Public/webuploader/0.1.5/server/fileupload.php. 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-260776. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary

dbcve analysis · high confidence

Vesystem Cloud Desktop up to 20240408 contains an unrestricted file upload vulnerability in /Public/webuploader/0.1.5/server/fileupload.php. The application fails to validate or restrict the file argument during upload, allowing remote attackers to upload arbitrary files including potentially malicious scripts to the server.

MitigationImplement strict file upload validation including allowlist-based file type checking, file content/magic byte verification, renaming uploaded files, and storing uploads outside the webroot or in a non-executable directory.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify Vesystem Cloud Desktop installation

Locate the Vesystem Cloud Desktop application on the system and determine its installed version. Check installation directories, software inventory, or the application itself for version information. Compare the installed version to the affected range (any version up to and including 20240408).

Affected if Vesystem Cloud Desktop is installed and the version is 20240408 or earlier.
Locate the vulnerable upload script

Search for the file /Public/webuploader/0.1.5/server/fileupload.php within the web application directory structure. This path is relative to the web root of the Vesystem Cloud Desktop installation.

Affected if The file /Public/webuploader/0.1.5/server/fileupload.php exists on the server.
Verify the upload endpoint is accessible

Check if the URL path /Public/webuploader/0.1.5/server/fileupload.php is reachable via HTTP/HTTPS from the application server or externally. This can be done by attempting a GET request to the endpoint or reviewing web server access logs.

Affected if The upload script is accessible via web request and responds to requests.
Inspect upload storage configuration

Examine the web server and application configuration to determine where uploaded files are stored. Check if the storage directory is within the webroot and if files retain executable extensions (.php, .asp, .exe, etc.).

Affected if Uploaded files are stored in a directory accessible via the web and retain their original file extensions, allowing potential execution.

A system is affected if Vesystem Cloud Desktop version 20240408 or earlier is installed, the vulnerable fileupload.php script exists and is accessible, and uploaded files can be stored in an executable location.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Implement strict file upload validation including allowlist-based file type checking, file content/magic byte verification, renaming uploaded files, and storing uploads outside the webroot or in a non-executable directory.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing3.0 h
Review / QA2.0 h

14.0 hours of engineering $2,490

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3803 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-3803?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 6.3 Medium

Exploit likelihood EPSS, next 30 days 0.5%

Remediation

Need this fixed?

Have this fixed 14 hrs · Moderate

Typical engagement from $2,490

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-3803 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References