dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-11617

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Envolve Plugin plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'zetra_languageUpload' and 'zetra_fontsUpload' functions in all versions up to, and including, 1.0. This makes it possible for unauthenticated attackers 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 Envolve Plugin for WordPress versions up to 1.0 contains arbitrary file upload vulnerabilities in the 'zetra_languageUpload' and 'zetra_fontsUpload' functions. These functions lack proper file type validation, allowing unauthenticated attackers to upload any file type including malicious executables that could lead to remote code execution.

MitigationImmediately remove or disable the Envolve Plugin if not essential. If the plugin is required, implement strict file type allowlisting, enforce authentication on upload endpoints, and store uploaded files outside the web root or with .php execution disabled.

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
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 checks

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

  1. Verify Envolve plugin is installed
    Check for the presence of the Envolve plugin directory in your WordPress installation at wp-content/plugins/envolve/ or similar plugin folder name. Use a file listing command or check via WordPress admin plugins page.
    Affected if The Envolve plugin directory exists in the WordPress plugins folder.
  2. Check installed Envolve plugin version
    Locate the main plugin file (usually index.php or envolve.php) or the readme.txt file within the plugin directory and read the declared version number.
    Affected if The installed version is 1.0 or any version up to and including 1.0.
  3. Identify vulnerable upload functions
    Search the plugin source code for the functions 'zetra_languageUpload' and 'zetra_fontsUpload' to confirm they exist and examine how they handle file uploads.
    Affected if These functions exist and contain file upload handling logic without proper file type validation.
  4. Verify upload endpoints are accessible
    Check if the plugin registers REST API routes, admin AJAX hooks, or direct PHP files that call the zetra_languageUpload or zetra_fontsUpload functions. Examine the plugin's main file and any dedicated upload handler files.
    Affected if The plugin exposes upload functionality through accessible endpoints (such as /wp-admin/admin-ajax.php or custom routes) without requiring authentication.
  5. Inspect file validation in upload handlers
    Review the upload code within zetra_languageUpload and zetra_fontsUpload functions for any file type checking, mime type validation, or allowlist/denylist logic. Look for functions like wp_check_filetype or similar validation.
    Affected if No file type validation exists, or validation can be easily bypassed (for example, only checking file extension without verifying actual file type).

If the Envolve plugin version is 1.0 or earlier and the zetra_languageUpload or zetra_fontsUpload functions are present and accessible without authentication, the environment is vulnerable to arbitrary file upload and potential remote code execution.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately remove or disable the Envolve Plugin if not essential. If the plugin is required, implement strict file type allowlisting, enforce authentication on upload endpoints, and store uploaded files outside the web root or with .php execution disabled.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

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