Divi <= 4.27.6 — Authenticated (Contributor+) Stored Cross-Site Scripting via Dynamic Content (Legacy JSON Format) Shortcode

Overview

Advisory ID

CVE-2026-3851

Product

Divi Divi

Affected

≤4.27.6

Fixed in

4.27.7

Weakness

CWE-79 Cross-Site Scripting

Required access

Unknown

Published

Sep 1, 2026 · updated Nov 13, 2026

Credit

Osvaldo Noe Gonzalez Del Rio (Os)

Source

Wordfence Intelligence

The Divi theme for WordPress is vulnerable to Stored Cross-Site Scripting via the Dynamic Content feature's legacy JSON format in all versions up to, and including, 4.27.6. This is due to two compounding flaws: (1) the save-time sanitization filter et_builder_sanitize_dynamic_content_fields() only searches for dynamic content markers in the @ET-DC@...@ format, but the rendering engine also supports a legacy JSON format that is silently converted at render time, completely bypassing the save-time filter, and (2) the post_meta_key resolver in et_builder_filter_resolve_default_dynamic_content() does not apply wp_kses_post() to the resolved meta value when enable_html is set to on, passing raw get_post_meta() output directly to the page. 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.

Not sure which version you run? Run a passive check — it reads public files only.

Remediation & mitigations

1. Update to version 4.27.7, or a newer patched version
2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.