dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-4345

CRITICAL · 9.8 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 uploads due to insufficient file type validation in the 'process' function in the 'startklarDropZoneUploadProcess' class in versions up to, and including, 1.7.13. 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 Startklar Elementor Addons WordPress plugin versions up to 1.7.13 contains an unauthenticated arbitrary file upload vulnerability in the startklarDropZoneUploadProcess class. The 'process' function lacks proper file type validation, allowing attackers to upload any file type including PHP scripts to achieve remote code execution.

MitigationUpdate the plugin to version 1.7.14 or later immediately. As an interim measure, disable the plugin or restrict access to the upload endpoint via web server configuration until the update can be applied.

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. Confirm plugin is installed
    Check if the Startklar Elementor Addons plugin exists in your WordPress plugins directory (wp-content/plugins/) or in the WordPress admin Plugins page
    Affected if The plugin is present in the installation
  2. Identify installed version
    View the main plugin file header (usually startklar-elementor-addons.php or similar in wp-content/plugins/) to read the Version field, or check the Plugins page in WordPress admin
    Affected if The version is 1.7.13 or lower
  3. Locate vulnerable class file
    Search the wp-content/plugins/ directory for files containing 'startklarDropZoneUploadProcess' class definition, typically in a file handling uploads
    Affected if The class file exists and contains the vulnerable 'process' function
  4. Check upload endpoint exposure
    Examine WordPress AJAX endpoints (admin-ajax.php) or custom upload handlers that the plugin registers; look for routes tied to the startklarDropZone upload functionality
    Affected if The upload endpoint is publicly accessible without authentication (the CVE specifies unauthenticated)
  5. Audit uploaded files for PHP scripts
    Review the designated upload directory (commonly wp-content/uploads/ or a plugin-specific subdirectory) for recently added .php files or other executable file types that were not intentionally uploaded
    Affected if Unexpected PHP files or scripts are found in upload directories

You are affected if the Startklar Elementor Addons plugin version is 1.7.13 or lower and the upload functionality is accessible to unauthenticated users.

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 immediately. As an interim measure, disable the plugin or restrict access to the upload endpoint via web server configuration until the update can be applied.

Recommended fix High confidence

1.7.14 or later

  1. 1. Update the Startklar Elementor Addons plugin to version 1.7.14 or later through the WordPress admin dashboard under Plugins > All Plugins
  2. 2. Navigate to Plugins > Add New > Upload and upload the latest version if automatic update is not available
  3. 3. Alternatively, update via WP-CLI: wp plugin update startklar-elementor-addons
  4. 4. Verify the update was successful by checking the plugin version in the installed plugins list
  5. 5. Test file upload functionality if it is used on the site to ensure the fix does not break legitimate functionality

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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