Unlimited Elements For ElementorWordPress extension · Unlimited Elements
CVE-2024-13155
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 the plugin's Transparent Split Hero widget in all versions up to, and including, 1.5.140 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 widget: Transparent Split Hero 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 confidenceStored XSS vulnerability in the Transparent Split Hero widget of the Unlimited Elements For Elementor WordPress plugin. Authenticated attackers with contributor-level access can inject arbitrary JavaScript through unsanitized user-supplied attributes, which executes whenever users access injected 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.141CVSS 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 if Unlimited Elements For Elementor plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Unlimited Elements For Elementor' in the list. Note the installed version number displayed.Affected if Plugin is installed with version lower than 1.5.141
-
Verify the Transparent Split Hero widget is in useSearch your WordPress pages and posts for any instances where the Transparent Split Hero widget has been added. This can be done by viewing pages in the Elementor editor or searching the database for widget references.Affected if The Transparent Split Hero widget is present on any page or post in the site
-
Inspect widget settings for unsanitized attributesEdit each page containing the Transparent Split Hero widget in Elementor, select the widget, and review all text input fields in the widget settings panel. Look for any unexpected or suspicious attribute values that may contain script tags or unusual characters.Affected if Any widget settings contain raw user-supplied input with script tags or JavaScript event handlers (such as onload, onerror, onclick)
-
Check for injected scripts in rendered pagesView pages containing the Transparent Split Hero widget in a browser, right-click and view page source, then search for any script tags or inline JavaScript that was not intentionally added by an administrator.Affected if Unexpected script tags appear in the HTML source of pages using the widget
You are affected if the plugin version is below 1.5.141 AND the Transparent Split Hero widget is in use on your site, regardless of whether visible malicious content is present in widget settings.
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.141
Update to version 1.5.141 or later; if the patch doesn't apply automatically, manually delete and reinstall the Transparent Split Hero widget to remove the vulnerable code.
Unlimited Elements For Elementor version 1.5.141
- Update the Unlimited Elements For Elementor plugin to version 1.5.141 or later through the WordPress plugin dashboard or by downloading from the WordPress plugin repository
- After updating, delete the Transparent Split Hero widget from any pages or templates where it was used
- Re-add the Transparent Split Hero widget to repopulate it with the patched widget code
- Clear any caching plugins or server-side caches to ensure the patched version is served
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-13155 — 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-13155 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