dbcve.org
Prime SliderWordPress extension · Bdthemes

CVE-2024-1730

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-20
Fix available
A fix is available. Upgrade to 3.14.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Prime Slider – Addons For Elementor (Revolution of a slider, Hero Slider, Media Slider, Drag Drop Slider, Video Slider, Product Slider, Ecommerce Slider) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via urls in link fields, images from URLs, and html tags used in widgets in all versions up to, and including, 3.14.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Prime Slider plugin for WordPress fails to properly sanitize and escape user inputs in link field URLs, images from URLs, and HTML tags within widgets. This allows authenticated attackers with contributor-level or higher permissions to inject malicious JavaScript that executes when other users access affected pages.

MitigationUpdate the Prime Slider plugin to a version beyond 3.14.0 once the vendor releases a patch addressing the input sanitization and output escaping issues.

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.14.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Bdthemes Prime Slider' or 'Prime Slider' in the list
    Affected if The plugin is not present in the plugins list, meaning it is not installed and therefore not affected
  2. Check installed Prime Slider version
    In WordPress admin, go to Plugins > Installed Plugins, find Prime Slider, and note the version number displayed below the plugin name. Alternatively, check the main plugin file header for the Version field
    Affected if The installed version is lower than 3.14.1 (e.g., 3.13.0, 3.12.5, etc.)
  3. Identify users with contributor-level or higher access
    In WordPress admin, go to Users and review the role column. Look for users assigned roles of Contributor, Author, Editor, or Administrator
    Affected if At least one user account has Contributor, Author, Editor, or Administrator role, providing the authentication level needed to exploit the vulnerability
  4. Check for widgets using link fields, URL images, or raw HTML
    In WordPress admin, go to Appearance > Widgets or the relevant widget area. Review any Prime Slider widgets configured, specifically looking for: link URL fields, image fields set to URL source, and any widget areas that may contain HTML widgets alongside Prime Slider content
    Affected if Prime Slider widgets are actively used with link URL fields, external image URLs, or exist in pages/posts alongside HTML content that could be exploited

The environment is affected if Prime Slider plugin is installed with a version below 3.14.1 and there are users with contributor-level permissions or higher, combined with active use of vulnerable widget features like link fields or URL-based images.

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.14.1 or later
Fixed in 3.14.1
Interim mitigation

Update the Prime Slider plugin to a version beyond 3.14.0 once the vendor releases a patch addressing the input sanitization and output escaping issues.

Recommended fix High confidence

3.14.1

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Prime Slider (Addons For Elementor) in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 3.14.1
  5. Alternatively, go to Plugins > Add New > Upload and upload version 3.14.1 of the plugin
  6. Verify the plugin version is 3.14.1 or higher after updating

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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