dbcve.org
Prime SliderWordPress extension · Bdthemes

CVE-2024-1508

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to 3.13.3 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 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'settings['title_tags']' attribute of the Mercury widget in all versions up to, and including, 3.13.2 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 contains a stored XSS vulnerability in the Mercury widget's title_tags parameter. Due to insufficient input sanitization and inadequate output escaping, authenticated users with contributor-level permissions can inject arbitrary JavaScript that executes when other users access affected pages.

MitigationUpdate Prime Slider plugin to version 3.13.3 or later to obtain the patched version that properly sanitizes the title_tags input and escapes output.

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
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. Check Prime Slider plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Bdthemes Prime Slider and read the version number. Alternatively, check the main plugin file header in /wp-content/plugins/prime-slider/
    Affected if The installed version is lower than 3.13.3
  2. Identify Mercury widget usage
    Navigate to the WordPress page builder (Elementor or similar) and search for the Prime Slider widgets. Look specifically for the Mercury widget being added to any page or post.
    Affected if The Mercury widget from Prime Slider is present on any published page or post
  3. Inspect title_tags parameter
    Edit any page using the Mercury widget. In the widget settings panel, locate the Title Tags or similar field under the widget options. Examine the current value stored in this parameter.
    Affected if The title_tags field contains unsanitized HTML or JavaScript such as <script> tags, event handlers like onmouseover, or javascript: URIs
  4. Check for injected malicious content
    Export or manually review the postmeta table entries for pages using the Mercury widget. Query for meta_key containing 'prime_slider' and inspect meta_value for any encoded or raw script tags, img onerror attributes, or similar XSS vectors in the title_tags field.
    Affected if Database contains XSS payloads in Prime Slider metadata related to the title_tags parameter

Environment is affected if Prime Slider version is below 3.13.3 AND the Mercury widget with title_tags parameter is in use on any published content, regardless of whether malicious payload has been injected yet.

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 plugin to version 3.13.3 or later to obtain the patched version that properly sanitizes the title_tags input and escapes output.

Recommended fix High confidence

Prime Slider plugin version 3.13.3

  1. Backup your WordPress site before making any changes
  2. Navigate to the WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Find 'Prime Slider – Addons For Elementor' in the plugin list
  5. Click 'Update now' if an update is available, or manually upload version 3.13.3 of the plugin
  6. Verify the plugin updated successfully to version 3.13.3
  7. Clear any caching mechanisms if enabled to ensure the fix takes effect

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

Fix this in Prime Slider Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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