# CVE-2024-13155: Cross-site scripting in Unlimited Elements For Elementor

> Authenticated contributors can inject arbitrary scripts via the Transparent Split Hero widget, leading to stored XSS execution for other users.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-qf3h-q4g6-359h

## What is CVE-2024-13155?

CVE-2024-13155 is a medium-severity cross-site scripting vulnerability in unitecms Unlimited Elements For Elementor, published on 20 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-13155?

It affects 1 product.


Products: Unlimited-Elements Unlimited Elements for Elementor.

## How do I fix CVE-2024-13155?

No fix has been published for CVE-2024-13155 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-13155 being exploited?

There is no known exploitation of CVE-2024-13155 in the wild and no public exploit code.

## Other vulnerabilities in unitecms Unlimited Elements For Elementor

- [CVE-2023-31090](https://insights.sbomify.com/CVE-2023-31090/): WordPress Unlimited Elements For Elementor plugin <= 1.5.60 - Unrestricted Zip Extraction vulnerability (critical 9.9)
- [CVE-2023-31231](https://insights.sbomify.com/CVE-2023-31231/): File upload in Unlimited Elements For Elementor (Free Widgets, Addons, Templates) (critical 9.9)
- [CVE-2024-49271](https://insights.sbomify.com/CVE-2024-49271/): Deserialization in Unlimited Elements For Elementor (Free Widgets, Addons, Templates) (critical 9.1)
- [CVE-2023-33930](https://insights.sbomify.com/CVE-2023-33930/): WordPress Unlimited Elements For Elementor plugin <= 1.5.66 - Unrestricted Zip Extraction vulnerability (critical 9.1)
- [CVE-2024-5329](https://insights.sbomify.com/CVE-2024-5329/): SQL injection in Unlimited Elements For Elementor (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13155 and fix it if it is affected.

What it is: CVE-2024-13155 is a medium-severity cross-site scripting vulnerability in unitecms Unlimited Elements For Elementor, published on 20 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13155 in the wild and no public exploit code.

Affected product: unitecms Unlimited Elements For Elementor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-13155/ (Markdown: https://insights.sbomify.com/CVE-2024-13155/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-13155
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-13155
- OSV: https://osv.dev/vulnerability/CVE-2024-13155

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-13155/
Summaries are generated and may contain mistakes; the official description above is the record.