Prime SliderWordPress extension · Bdthemes
CVE-2024-30186
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in BdThemes Prime Slider – Addons For Elementor allows Stored XSS.This issue affects Prime Slider – Addons For Elementor: from n/a through 3.13.1.
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 confidenceStored XSS vulnerability in BdThemes Prime Slider plugin for Elementor allows attackers to inject malicious scripts through unsanitized user input that gets stored and executed when other users view the affected content.
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
< 3.13.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Prime Slider versionIn WordPress admin, go to Plugins > BdThemes Prime Slider and view the version number displayed, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'elementor_prime_slider_version' OR check the plugin header in /wp-content/plugins/prime-slider/includes/class-ps-module-base.phpAffected if The installed version is lower than 3.13.2
-
Confirm plugin is activeQuery WordPress active plugins: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%prime-slider%'Affected if Prime Slider plugin appears in the active plugins list and the version is below 3.13.2
-
Inspect Elementor content using Prime Slider widgetsSearch WordPress postsmeta for Elementor data containing 'prime-slider': SELECT * FROM wp_postmeta WHERE meta_value LIKE '%prime-slider%' LIMIT 50Affected if Any Elementor content exists using Prime Slider widgets on a vulnerable version
-
Check for injected script tags in stored contentSearch wp_postmeta for suspicious script tags or event handlers: SELECT * FROM wp_postmeta WHERE (meta_value LIKE '%<script%' OR meta_value LIKE '%onerror=%' OR meta_value LIKE '%onload=%' OR meta_value LIKE '%javascript:%') AND meta_value LIKE '%prime%'Affected if Any records contain script tags, javascript: URIs, or event handlers like onerror/onload in Prime Slider-related stored data
The environment is affected if Prime Slider version is below 3.13.2 AND the plugin is active AND Elementor content uses Prime Slider widgets with any unsanitized user input stored in the database.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.13.2
Update to the latest version of Prime Slider – Addons For Elementor after verifying the patch addresses input sanitization, or implement proper output encoding on all user-supplied data before rendering in web pages.
3.13.2
- Backup your WordPress site before making any changes
- Update Prime Slider – Addons For Elementor plugin to version 3.13.2 or later through the WordPress plugin repository or your preferred update method
- Verify the update was successfully applied by checking the plugin version in WordPress admin > Plugins
- Clear any caching mechanisms if applicable to ensure the patched version is served
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Prime Slider
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30186 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-30186 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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