dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-11082

CRITICAL · 9.9 CVSS v3.1 Published 2024-11-28
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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
The Tumult Hype Animations plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the hypeanimations_panel() function in all versions up to, and including, 1.9.15. This makes it possible for authenticated attackers, with Author-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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

The Tumult Hype Animations WordPress plugin (versions up to 1.9.15) lacks file type validation in the hypeanimations_panel() function, allowing authenticated users with Author-level or higher permissions to upload arbitrary files to the server, enabling potential remote code execution.

MitigationUpdate the plugin to the latest version once available, or implement strict file type validation and upload directory restrictions in the hypeanimations_panel() function to prevent arbitrary file uploads.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Confirm plugin installation and version
    Navigate to WordPress admin > Plugins and locate 'Tumult Hype Animations', or inspect the plugin header in wp-content/plugins/hype-animations/hype-animations.php to read the Version field
    Affected if The installed version is 1.9.15 or lower, or the Version field is missing/unreadable indicating an older release
  2. Identify the vulnerable function file
    Locate the file containing hypeanimations_panel() function - typically in the plugin directory under files such as admin/hypeanimations_panel.php or within the main plugin file, using grep or file search for the string 'function hypeanimations_panel'
    Affected if The hypeanimations_panel() function exists in the installed plugin files
  3. Verify file upload logic in the vulnerable function
    Open the file containing hypeanimations_panel() and inspect the code for file upload handling - look for $_FILES, move_uploaded_file, or wp_handle_upload calls without file type validation using wp_check_filetypes or similar validation functions
    Affected if File upload code exists without proper file type validation (no mime type checking, no extension whitelist, or no use of wp_check_filetypes)
  4. Check user role permissions for the vulnerable action
    In WordPress admin, go to Users > All Users and review which users have Author-level or higher roles; alternatively, inspect the hypeanimations_panel() function for capability checks like 'edit_posts' or 'upload_files'
    Affected if Any user account with Author, Editor, or Administrator role exists on the WordPress site, as these roles can access the vulnerable function
  5. Confirm the upload directory is accessible
    Check if the plugin's upload directory (typically wp-content/uploads/hypeanimations/ or similar) exists and is writable by inspecting directory permissions or accessing the path via the browser
    Affected if The upload directory exists and is web-accessible with write permissions

A user is affected if the Tumult Hype Animations plugin version is 1.9.15 or lower, the hypeanimations_panel() function exists without file type validation, and at least one Author-level or higher user account exists on the WordPress site.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Update the plugin to the latest version once available, or implement strict file type validation and upload directory restrictions in the hypeanimations_panel() function to prevent arbitrary file uploads.

Recommended fix Moderate confidence

1.9.16

  1. 1. Update the Tumult Hype Animations plugin to version 1.9.16 or later via the WordPress admin dashboard under Plugins > All Plugins > Tumult Hype Animations > Update Now
  2. 2. Verify the update was successful by checking the plugin version number
  3. 3. Confirm the hypeanimations_panel() function now properly validates file types before allowing uploads
  4. 4. Review user accounts with Author-level access and above to ensure only trusted users have upload capabilities

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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