dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-4389

HIGH · 8.8 CVSS v3.1 Published 2024-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Slider and Carousel slider by Depicter plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the uploadFile function in all versions up to, and including, 3.1.1. This makes it possible for authenticated attackers, with contributor access or higher, 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 Depicter WordPress plugin has an arbitrary file upload vulnerability in its uploadFile function due to missing file type validation in all versions up to 3.1.1. Authenticated attackers with contributor-level access or higher can upload arbitrary files to the server, potentially achieving remote code execution.

MitigationUpdate the Depicter plugin to version 3.1.2 or later immediately. Until patched, consider restricting user permissions and monitoring for suspicious upload activity.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Depicter plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Depicter' in the list. Alternatively, check the /wp-content/plugins/depicher/ directory exists on the server.
    Affected if Depicter plugin is present in the WordPress installation
  2. Determine installed Depicter version
    In WordPress admin, find Depicter in the plugins list and read the version number under the plugin name. Or check the version in /wp-content/plugins/depicter/readme.txt or the plugin header in /wp-content/plugins/depicter/depicter.php.
    Affected if Version is 3.1.1 or earlier (versions up to and including 3.1.1 are affected)
  3. Check for contributor-level or higher user accounts
    In WordPress admin, go to Users and review the role assigned to each account. Contributor, Author, Editor, and Administrator roles all have contributor-level access or higher.
    Affected if Any user account with Contributor, Author, Editor, or Administrator role exists (these roles can exploit the vulnerability)
  4. Verify uploadFile function is accessible
    Check if the file /wp-content/plugins/depicter/vendor/averta/wp-dependency-layer/src/classes/Upload.php or similar upload handling files exist and are readable. The vulnerability exists in the uploadFile function within the plugin.
    Affected if The upload functionality file exists and is accessible (the vulnerable code is present)

A user is affected if the Depicter plugin versions 3.1.1 or earlier are installed AND at least one user with contributor-level or higher access exists in 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Depicter plugin to version 3.1.2 or later immediately. Until patched, consider restricting user permissions and monitoring for suspicious upload activity.

Recommended fix Moderate confidence

Version 3.1.2 or later (check WordPress plugin repository for latest stable release)

  1. 1. Log in to WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find the 'Slider and Carousel slider by Depicter' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest patched version
  5. 5. After updating, verify the upload functionality works correctly and that the site functions as expected
Caveat Minor release upgrade; review changelog for any functionality changes before updating on production sites

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-4389 — 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-4389 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