# CVE-2024-4580: Cross-site scripting in Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits

> Authenticated contributors can inject arbitrary scripts into WordPress pages via the Master Addons plugin, leading to stored XSS attacks.

- **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:** 16 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2p4r-h63c-pgmr

## What is CVE-2024-4580?

CVE-2024-4580 is a medium-severity cross-site scripting vulnerability in litonice13 Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits, published on 16 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Master Addons – Free Widgets, Hover Effects, Toggle, Conditions, Animations for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via several parameters in versions up to, and including, 2.0.6.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE-2024-35702 is likely a duplicate of this issue.

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

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

It affects 1 product.


Products: Master-Addons Master Addons.

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

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

## Is CVE-2024-4580 being exploited?

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

## Other vulnerabilities in litonice13 Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits

- [CVE-2024-5542](https://insights.sbomify.com/CVE-2024-5542/): Cross-site scripting in Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits (high 7.2)
- [CVE-2024-35660](https://insights.sbomify.com/CVE-2024-35660/): WordPress Master Addons for Elementor plugin <= 2.0.5.4.1 - Broken Access Control on API vulnerability (medium 6.5)
- [CVE-2024-35688](https://insights.sbomify.com/CVE-2024-35688/): WordPress Master Addons for Elementor plugin <= 2.0.5.9 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2024-35702](https://insights.sbomify.com/CVE-2024-35702/): WordPress Master Addons for Elementor plugin <= 2.0.6.0 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2024-5382](https://insights.sbomify.com/CVE-2024-5382/): Missing authorization in Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4580 is a medium-severity cross-site scripting vulnerability in litonice13 Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits, published on 16 May 2024. 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-4580 in the wild and no public exploit code.

Affected product: litonice13 Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits. 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-4580/ (Markdown: https://insights.sbomify.com/CVE-2024-4580/index.md)
```

## Sources

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

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