dbcve.org
Prime SliderWordPress extension · Bdthemes

CVE-2024-32681

HIGH · 8.8 CVSS v3.1 Published 2024-04-22
Fix available
A fix is available. Upgrade to 3.13.3 or later.
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
Missing Authorization vulnerability in BdThemes Prime Slider – Addons For Elementor.This issue affects Prime Slider – Addons For Elementor: from n/a through 3.13.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

This is a Missing Authorization vulnerability in the BdThemes Prime Slider plugin for Elementor. The vulnerability allows attackers to bypass access controls and access functionality they should not have permission to use. This is a classic IDOR or broken access control issue where the application fails to verify user authorization before performing sensitive operations.

MitigationUpdate Prime Slider – Addons For Elementor to version 3.13.2 or later, which contains the patched version. Additionally, ensure proper role-based access control (RBAC) is enforced on all sensitive endpoints within the plugin.

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
Prime SliderWordPress extension
Affected:< 3.13.3

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 Prime Slider plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) or navigate to Plugins > Installed Plugins in the WordPress admin dashboard and look for 'Prime Slider - Addons For Elementor' or 'BdThemes Prime Slider'
    Affected if The plugin is present in the installation
  2. Identify the installed version of Prime Slider
    In WordPress admin, go to Plugins > Installed Plugins, find Prime Slider, and note the version number displayed below the plugin name. Alternatively, inspect the main plugin file (prime-slider.php) in wp-content/plugins/prime-slider/ and look for the 'Version' header comment
    Affected if Version number is less than 3.13.3
  3. Compare against vulnerable version range
    Take the identified version (e.g., 3.13.2, 3.12.0, etc.) and compare it numerically to 3.13.3. Any version below 3.13.3 is affected
    Affected if Installed version is 3.13.2 or lower, or any 3.x version below 3.13.3
  4. Check WordPress user role configuration
    Review WordPress user roles and capabilities at Users > All Users to understand which roles have access to Prime Slider settings and widget controls
    Affected if Lower-privileged users (subscribers, contributors) exist and could potentially exploit the authorization bypass

The environment is affected if BdThemes Prime Slider is installed and the installed version is any release prior to 3.13.3.

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.13.3 or later
Fixed in 3.13.3
Interim mitigation

Update Prime Slider – Addons For Elementor to version 3.13.2 or later, which contains the patched version. Additionally, ensure proper role-based access control (RBAC) is enforced on all sensitive endpoints within the plugin.

Recommended fix High confidence

Prime Slider – Addons For Elementor version 3.13.3 or later

  1. 1. Create a full backup of your WordPress site (database and files) before making any changes.
  2. 2. Navigate to your WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate 'Prime Slider – Addons For Elementor' in the plugin list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.13.3 or later.
  5. 5. Alternatively, download version 3.13.3 or later from the WordPress plugin repository and upload/install it manually.
  6. 6. After updating, verify the plugin version displays as 3.13.3 or higher in the Plugins admin page.
  7. 7. Test the slider functionality on your site to ensure the update did not break existing functionality.

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

Fix this in Prime Slider Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

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