Unlimited Elements For ElementorWordPress extension · Unlimited Elements
CVE-2024-13153
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 · uneditedThe Unlimited Elements For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple widgets in all versions up to, and including, 1.5.135 due to insufficient input sanitization and output escaping on user supplied attributes. 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. Note: Since the widget code isn't part of the code base, to apply the patch, the affected widgets: Image Tooltip, Notification, Simple Popup, Video Play Button, and Card Carousel, must be deleted and reinstalled manually.
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 confidenceThe Unlimited Elements For Elementor WordPress plugin fails to properly sanitize and escape user-supplied attributes in five widgets (Image Tooltip, Notification, Simple Popup, Video Play Button, and Card Carousel), allowing authenticated attackers with contributor-level or higher access to inject persistent malicious JavaScript that executes when other users access affected pages.
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
Unlimited Elements For ElementorWordPress extension
< 1.5.136CVSS 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 plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Unlimited Elements For Elementor and note the version number displayed. Alternatively, check the plugin's main PHP file header or the readme.txt file in the plugin directory for the Version field.Affected if The version is less than 1.5.136 (any version from 1.0.0 through 1.5.135 is affected)
-
Identify active use of Image Tooltip widgetIn Elementor editor, search pages/posts for the Image Tooltip widget. Also check Elementor saved templates and theme builder conditions where this widget may be placed.Affected if The widget is present on any published page, post, or template AND the plugin version is below 1.5.136
-
Identify active use of Notification widgetIn Elementor editor, search pages/posts for the Notification widget. Check all custom post types, pages, and Elementor templates where this widget may be placed.Affected if The widget is present on any published page, post, or template AND the plugin version is below 1.5.136
-
Identify active use of Simple Popup widgetIn Elementor editor, search pages/posts for the Simple Popup widget. Also check global widget settings and popup conditions in Elementor.Affected if The widget is present on any published page, post, or template AND the plugin version is below 1.5.136
-
Identify active use of Video Play Button widgetIn Elementor editor, search pages/posts for the Video Play Button widget. Check all landing pages and content areas where this widget may be embedded.Affected if The widget is present on any published page, post, or template AND the plugin version is below 1.5.136
-
Identify active use of Card Carousel widgetIn Elementor editor, search pages/posts for the Card Carousel widget. Check all sections where carousel widgets are used.Affected if The widget is present on any published page, post, or template AND the plugin version is below 1.5.136
You are affected if the Unlimited Elements For Elementor plugin version is below 1.5.136 AND any of the five widgets (Image Tooltip, Notification, Simple Popup, Video Play Button, or Card Carousel) are in active use on your site.
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 · scoped1.5.136
Update the plugin to version 1.5.135 or later, then manually delete and reinstall the five affected widgets (Image Tooltip, Notification, Simple Popup, Video Play Button, and Card Carousel) to remove the vulnerable code.
1.5.136 or later
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Unlimited Elements For Elementor' plugin
- Check if current version is below 1.5.136
- If update available, click 'Update Now' to upgrade to version 1.5.136 or later
- After updating, delete the affected widgets manually: Image Tooltip, Notification, Simple Popup, Video Play Button, and Card Carousel
- Reinstall the deleted widgets from the Unlimited Elements library to ensure the patched versions are in use
- Clear any caching plugins or server-side caches
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Unlimited Elements For Elementor
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13153 — 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-13153 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