CVE-2024-11615
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 · uneditedThe Envolve Plugin plugin for WordPress is vulnerable to arbitrary file deletion in all versions up to, and including, 1.0 via the 'zetra_deleteLanguageFile' and 'zetra_deleteFontsFile' functions. This is due to the plugin not properly validating a file or its path prior to deleting it. This makes it possible for unauthenticated attackers to delete language files.
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 confidenceThe Envolve Plugin for WordPress versions up to 1.0 contains an arbitrary file deletion vulnerability in the zetra_deleteLanguageFile and zetra_deleteFontsFile functions. These functions fail to properly validate file paths before deletion, allowing unauthenticated attackers to delete arbitrary files on the server.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
-
Check if Envolve Plugin is installedInspect the WordPress plugins directory at wp-content/plugins/ for a folder named 'envolve', 'tetra', or similar Envolve-related naming. Also check wp_options table for active_plugins entry containing 'envolve' or 'tetra'.Affected if The Envolve Plugin folder exists in the WordPress plugins directory and the plugin is active in WordPress
-
Verify the Envolve Plugin versionOpen the main plugin PHP file (typically in the plugin root folder) and read the plugin header comment to find the 'Version:' value. Compare this to '1.0' - any version at or below 1.0 is affected.Affected if The plugin version is 1.0 or any version lower than 1.0 (the CVE states versions up to 1.0 are affected)
-
Confirm vulnerable functions existSearch all PHP files within the Envolve Plugin folder for the function names 'zetra_deleteLanguageFile' and 'zetra_deleteFontsFile'. Use grep or open the files directly.Affected if Both functions zetra_deleteLanguageFile and zetra_deleteFontsFile exist in the plugin code without proper path validation checks
-
Check if the plugin is accessible to unauthenticated usersReview the plugin code to determine if the vulnerable delete functions are hooked to WordPress actions accessible to visitors or users without admin privileges (such as wp_ajax_nopriv_ hooks or publicly accessible admin-post.php endpoints).Affected if The file deletion functions can be triggered by unauthenticated (not-logged-in) users
The environment is affected if the Envolve Plugin is installed at version 1.0 or below, contains the zetra_deleteLanguageFile or zetra_deleteFontsFile functions, and those functions are accessible without authentication.
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 dataRemove or disable the Envolve Plugin until a patched version is available. Implement proper path traversal validation and authentication checks in the affected functions.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11615 — 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-11615 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