CVE-2026-6127 json
Elementor Website Builder <= 4.0.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via REST API
published 2026-05-01 6 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-26479
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
The Elementor Website Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the _elementor_data meta field in versions up to, and including, 4.0.4. This is due to insufficient input sanitization when processing form-encoded REST API requests. The plugin registers the _elementor_data meta field with show_in_rest but omits a sanitize_callback, relying instead on a rest_pre_insert_post filter (sanitize_post_data function) that only sanitizes JSON-encoded request bodies. When a contributor sends a form-encoded PATCH request to the WordPress REST API, the json_decode() call on the raw body returns null, causing all sanitization to be skipped. The unsanitized data is then stored via update_post_meta() and later output without escaping through multiple widget sinks including the HTML widget's print_unescaped_setting() function. 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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
Affected products
- elemntor Elementor Website Builder – more than just a page builder
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/826a2003-c526-4760-8c21-10d5ae7bb384?source=cve
- plugins.trac.wordpress.org /browser/elementor/trunk/includes/base/widget-base.php#L794
- plugins.trac.wordpress.org /browser/elementor/tags/4.0.1/includes/base/widget-base.php#L794
- plugins.trac.wordpress.org /browser/elementor/trunk/includes/plugin.php#L840
- plugins.trac.wordpress.org /browser/elementor/tags/4.0.1/includes/plugin.php#L840
- plugins.trac.wordpress.org /browser/elementor/trunk/modules/wp-rest/classes/elementor-post-meta.php#L68
- plugins.trac.wordpress.org /browser/elementor/tags/4.0.1/modules/wp-rest/classes/elementor-post-meta.php#L68
- plugins.trac.wordpress.org /changeset/3519457/
Sources
- CVE List CVE-2026-6127
- NVD CVE-2026-6127
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.