dbcve.org
DepicterWordPress extension

CVE-2024-47359

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 3.5.0 or later.
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
Cross-Site Request Forgery (CSRF) vulnerability in averta Depicter Slider depicter.This issue affects Depicter Slider: from n/a through <= 3.2.2.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Depicter Slider WordPress plugin (versions <= 3.2.2) allows remote attackers to trick authenticated administrators into executing unintended actions by forging requests to vulnerable endpoints.

MitigationUpdate Depicter Slider to the latest patched version when available, or implement anti-CSRF token validation on all state-changing AJAX and form endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DepicterWordPress extension
Affected:< 3.5.0

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 Depicter plugin is installed
    Access WordPress admin dashboard under Plugins or inspect plugin directory /wp-content/plugins/depicter/ for plugin files
    Affected if The Depicter plugin is present in the WordPress installation
  2. Identify installed Depicter version
    Check the plugin header in main plugin file (commonly /wp-content/plugins/depicter/depicter.php) for 'Version:' value, or view version in WordPress Plugins admin page
    Affected if Version is less than 3.5.0 (including all versions <= 3.2.2)
  3. Confirm vulnerable AJAX endpoints lack CSRF protection
    Inspect source code of plugin AJAX handlers (look for wp_ajax_ and wp_ajax_nopriv_ hooks) and verify if nonce verification or check_ajax_referer is missing before state-changing operations
    Affected if Admin AJAX endpoints perform actions without validating nonce tokens or CSRF tokens
  4. Identify state-changing endpoints accessible to authenticated admins
    Review plugin code for form submissions, database write operations, or settings changes triggered via admin-initiated requests without protective tokens
    Affected if Endpoints that modify slider data, settings, or plugin configuration accept requests without anti-CSRF validation

If Depicter Slider version is below 3.5.0 and admin-facing AJAX/form endpoints lack nonce or CSRF token validation, the installation is affected by this CSRF vulnerability.

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
Upgrade available Upgrade to 3.5.0 or later
Fixed in 3.5.0
Interim mitigation

Update Depicter Slider to the latest patched version when available, or implement anti-CSRF token validation on all state-changing AJAX and form endpoints.

Recommended fix High confidence

3.5.0 or later

  1. 1. Backup your WordPress site before making any changes.
  2. 2. Navigate to WordPress Dashboard > Plugins > Installed Plugins.
  3. 3. Locate the Depicter Slider plugin in the list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.5.0 or later.
  5. 5. Alternatively, download the latest version from the official WordPress repository or the plugin vendor and upload it manually.
  6. 6. After updating, verify the plugin version shows 3.5.0 or higher.
  7. 7. Test the slider functionality to ensure the update did not break any existing features.

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

Fix this in Depicter Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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