CVE-2024-0916
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 · uneditedUnauthenticated file upload allows remote code execution. This issue affects UvDesk Community: from 1.0.0 through 1.1.3.
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 confidenceUvDesk Community versions 1.0.0 through 1.1.3 contain an unauthenticated file upload vulnerability allowing remote attackers to upload malicious files (e.g., web shells) to the server, which can then be executed for complete system compromise.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Verify UvDesk Community is installedCheck for UvDesk Community application by looking for its characteristic directory structure (typically in web root, search for 'uvdesk' folder or composer.json with uvdesk package)Affected if The application is present on the server
-
Determine installed UvDesk Community versionLocate the version file - typically in a composer.lock file or a version configuration file within the UvDesk installation directory. Compare the version number against the affected range 1.0.0 to 1.1.3Affected if The installed version falls within 1.0.0 through 1.1.3 (inclusive)
-
Confirm file upload functionality is accessibleIdentify if the file upload endpoint is publicly accessible without authentication - UvDesk has ticket attachment features. Check if the web server allows incoming requests to upload-related routes (typically /upload or /attachments paths)Affected if File upload routes are exposed to unauthenticated users
-
Inspect upload directories for suspicious filesSearch common upload directories within the UvDesk installation for newly created files with executable extensions (.php, .phtml, .php5, .phar, .exe). Review file creation timestamps for recent malicious uploadsAffected if Unknown or suspicious executable files exist in upload directories
-
Review web server and application logs for anomalous upload requestsExamine access logs for POST requests to upload endpoints originating from external IPs, especially those containing unusual file extensions or multiple upload attemptsAffected if Logs show unauthorized or suspicious file upload requests from unauthenticated sources
The environment is affected if UvDesk Community versions 1.0.0 through 1.1.3 are installed AND the file upload functionality is accessible, regardless of whether malicious files are yet present.
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.
dbcve · scopedUpgrade to a patched version of UvDesk Community. As an interim measure, disable or restrict file upload functionality and deploy WAF rules to block suspicious upload requests.
UvDesk Community 1.1.7 or later (any version after 1.1.3)
- Backup your UvDesk Community installation and database before proceeding
- Download or update to UvDesk Community version 1.1.7 or later from the official repository
- If using Composer, run 'composer update' to fetch the latest version
- Verify the file upload functionality is working correctly after the update
- Review the changes in PR #706 (https://github.com/uvdesk/core-framework/pull/706) to confirm the vulnerability is addressed
- Ensure file upload restrictions are enforced in your web server configuration as an additional defense layer
Generated from the published advisory — verify against the referenced sources before acting.
- 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-0916 — 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-0916 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