dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-4346

CRITICAL · 9.1 CVSS v3.1 Published 2024-05-07
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 Startklar Elementor Addons plugin for WordPress is vulnerable to arbitrary file deletion in all versions up to, and including, 1.7.13. This is due to the plugin not properly validating the path of an uploaded file prior to deleting it. This makes it possible for unauthenticated attackers to delete arbitrary files, including the wp-config.php file, which can make site takeover and 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 Startklar Elementor Addons WordPress plugin versions up to 1.7.13 contains an arbitrary file deletion vulnerability due to insufficient path validation in its file deletion functionality. Unauthenticated attackers can supply path traversal sequences (e.g., ../../wp-config.php) to delete any file on the server accessible by the web server process, including the critical wp-config.php configuration file.

MitigationUpdate the plugin to version 1.7.14 or later which contains proper path validation. Until updated, consider disabling the plugin or implementing web server-level access controls to block the vulnerable endpoint.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Locate the Startklar Elementor Addons plugin
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'startklar-elementor-addons' or inspect the plugin list via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder exists in the WordPress installation
  2. Determine the installed plugin version
    If accessing WordPress admin: go to Plugins > Installed Plugins and find the version listed under 'Startklar Elementor Addons'. Alternatively, inspect the main plugin file (usually startklar-elementor-addons.php) and look for a version comment or constant
    Affected if The version is 1.7.13 or lower (any version up to and including 1.7.13)
  3. Identify the vulnerable file deletion functionality
    Look for PHP files in the plugin directory that handle file operations, particularly any AJAX handlers or public-facing endpoints that accept file path parameters. Common patterns include functions named like 'delete_file', 'remove_file', or file upload handlers with deletion capability
    Affected if The plugin contains a file deletion function that accepts user-supplied paths without validating they are within an allowed directory

Your environment is affected if the Startklar Elementor Addons plugin is installed and its version is 1.7.13 or lower, since the vulnerability allows unauthenticated path traversal file deletion in the plugin's file handling code.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.7.14 or later which contains proper path validation. Until updated, consider disabling the plugin or implementing web server-level access controls to block the vulnerable endpoint.

Recommended fix Moderate confidence

1.7.14

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > All Plugins in the WordPress admin dashboard
  3. Find 'Startklar Elementor Addons' in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 1.7.14 or later
  5. Verify the updated version number after the update completes
  6. Test that the plugin functionality still works as expected

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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