# CVE-2022-29455: WordPress Elementor plugin <= 3.5.5 - Unauthenticated DOM-based Reflected Cross-Site Scripting (XSS) vulnerability

> Unauthenticated attackers can execute arbitrary JavaScript in victim browsers via DOM-based reflected XSS in the Elementor Website Builder plugin.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jun 2022
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-9gjm-mrgw-7qq8

## What is CVE-2022-29455?

CVE-2022-29455 is a medium-severity cross-site scripting vulnerability in Elementor Website Builder (WordPress plugin), published on 13 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

DOM-based Reflected Cross-Site Scripting (XSS) vulnerability in Elementor's Elementor Website Builder plugin <= 3.5.5 versions.

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

## Which versions are affected by CVE-2022-29455?

It affects 1 product.


Products: Elementor Website Builder.

## How do I fix CVE-2022-29455?

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

## Is CVE-2022-29455 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29455 exists.

Public exploit code:

- Wordpress Vulnerability - XSS ( Cross-Site Scripting ) (github_poc): https://github.com/akhilkoradiya/CVE-2022-29455
- https://github.com/GULL2100/Wordpress_xss-CVE-2022-29455 (github_poc): https://github.com/GULL2100/Wordpress_xss-CVE-2022-29455
- CVE-2022-29455 (github_poc): https://github.com/0xc4t/CVE-2022-29455
- Mass Scanner for CVE-2022-29455 on Elementor Plugins Wordpress (github_poc): https://github.com/abdipranata/CVE-2022-29455
- WordPress Elementor Website Builder <= 3.5.5 - DOM Cross-Site Scripting (nuclei): http/cves/2022/CVE-2022-29455.yaml

## Other vulnerabilities in Elementor Website Builder (WordPress plugin)

- [CVE-2023-48777](https://insights.sbomify.com/CVE-2023-48777/): WordPress Elementor plugin 3.3.0-3.18.1 - Arbitrary File Upload vulnerability (critical 9.9)
- [CVE-2020-7109](https://insights.sbomify.com/CVE-2020-7109/): Cross-site scripting in n/a (critical 9.8)
- [CVE-2022-1329](https://insights.sbomify.com/CVE-2022-1329/): Elementor Website Builder 3.6.0 - 3.6.2 - Missing Authorization to Remote Code Execution (high 8.8)
- [CVE-2024-24934](https://insights.sbomify.com/CVE-2024-24934/): WordPress Elementor plugin <= 3.19.0 - Arbitrary File Deletion and Phar Deserialization vulnerability (high 8.5)
- [CVE-2023-0329](https://insights.sbomify.com/CVE-2023-0329/): Elementor Website Builder < 3.12.2 - Admin+ SQLi (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29455 and fix it if it is affected.

What it is: CVE-2022-29455 is a medium-severity cross-site scripting vulnerability in Elementor Website Builder (WordPress plugin), published on 13 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29455 exists.

Affected product: Elementor Website Builder (WordPress plugin). 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-2022-29455/ (Markdown: https://insights.sbomify.com/CVE-2022-29455/index.md)
```

## Sources

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

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