We’re actively acquiring WordPress agencies. Sell your WordPress business to Freshy.
Let’s discuss

Elementor Website Builder Plugin Vulnerability (CVE-2026-6127)

Nick Paliughi
On this page

Security Alert Summary

The Elementor Website Builder plugin for WordPress has a stored cross-site scripting (XSS) vulnerability via the _elementor_data post meta when processing form-encoded REST API requests. Authenticated users with contributor-level access and above can cause unsanitized data to be saved and later output without escaping, allowing injected scripts to run when an affected page is viewed.

CVE Details

  • CVE ID: CVE-2026-6127
  • Affected component: Elementor Website Builder plugin for WordPress
  • Affected versions: versions up to, and including, 4.0.4
  • Published: May 1, 2026, 6:16:32 AM
  • Last modified: May 1, 2026, 3:26:24 PM
  • CVSS v3.1: Base Score 6.4 (MEDIUM) — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
  • Authentication / Privileges / User interaction: Requires authenticated user with low privileges (contributor-level access or above); no user interaction required.
  • Primary impact: Confidentiality: Low; Integrity: Low; Availability: None
  • Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-site Scripting)

Technical Details

This vulnerability is a stored cross-site scripting (XSS) issue stemming from insufficient input sanitization when the plugin processes form-encoded REST API requests. The plugin registers the _elementor_data post meta with show_in_rest but does not provide a sanitize_callback. Instead, it relies on a rest_pre_insert_post filter (the 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, a json_decode() call on the raw request body returns null, which causes the JSON-specific sanitization to be skipped. The unsanitized data is then stored using update_post_meta(). Later, the data may be output without escaping through multiple widget sinks, including the HTML widget’s print_unescaped_setting() function, enabling execution of injected scripts in pages that include the affected widget content.

The issue exists because form-encoded requests are not covered by the plugin’s sanitization path, allowing contributor-level authenticated users to persist HTML/JS payloads that are rendered unescaped.

How This Could Impact Your Website

In a realistic scenario, an internal contributor or an external contractor with contributor access could edit a page via the REST API using a form-encoded PATCH request and insert a malicious script into a widget setting. When that page is viewed by site staff, editors, or visitors, the script could execute in their browsers. Practical consequences include exposure of visible or accessible data on the page, an increased risk of targeted phishing or social engineering against staff who visit affected pages, and user session or cookie theft in cases where a victim’s browser permits it.

The CVSS impact ratings indicate confidentiality and integrity impacts are low, so this vulnerability should not be interpreted as an automatic full site compromise. If you’re unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review.

Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially contributor accounts that do not require content publishing privileges.
  • Enforce strong passwords and enable two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins and themes to reduce attack surface.
  • Monitor site activity and logs for unusual behavior, including unexpected REST API requests or changes to post meta fields.

If you’d like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.

References

Nick Paliughihttps://freshysites.com/team/nick-paliughi/
Nick was born in California and now resides in Lake Worth, FL. He has 10 years of experience building and maintaining sites in WordPress, which he is excited to put to use at Freshy. Prior to starting at Freshy in 2022 his focus was on WordPress security & malware removal. When he’s not tending to your website, Nick is installing exhibitions at art galleries and museums in Palm Beach County, and if he’s lucky surfing at the Lake Worth pier.

See our featured website design work

Check out some of the beautiful websites we’ve built for over 2,000 clients.

View projects

We offer WordPress support & maintenance

Shake the stress of ongoing maintenance with plans supported by our team of WordPress experts.

Learn more
Previous Post
Temporary Login Plugin Vulnerability (CVE-2026-7567)
Next Post
WP Editor Plugin Vulnerability (CVE-2026-3772)