# CVE-2026-81813: Elementor < 4.3.5 - Contributor+ Stored XSS via SVG CDATA Sanitizer Bypass


- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-grh6-fqc7-f8f5

## What is CVE-2026-81813?

CVE-2026-81813 is a medium-severity vulnerability in Unknown Elementor Website Builder, published on 21 Oct 2026. 

### Official description

The Elementor Website Builder  WordPress plugin before 4.3.5 does not sanitize the text content of SVG files, checking only their elements and attributes, allowing users with the Contributor role and above to store a payload which breaks out when the SVG is rendered inline in a page and executes in the browser of any user viewing it. Execution is specific to Chromium-based browsers; Firefox is not affected.

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

## Which versions are affected by CVE-2026-81813?


## How do I fix CVE-2026-81813?

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

## Is CVE-2026-81813 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81813 and fix it if it is affected.

What it is: CVE-2026-81813 is a medium-severity vulnerability in Unknown Elementor Website Builder, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-81813 in the wild and no public exploit code.

Affected product: Unknown Elementor Website Builder. 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-2026-81813/ (Markdown: https://insights.sbomify.com/CVE-2026-81813/index.md)
```

## Sources

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

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