Elegant mes Divi Plugin up to 4.27.6 on WordPress Dynamic Content feature enable_html cross site scripting

Summaryinfo

A vulnerability identified as problematic has been detected in Elegant mes Divi Plugin up to 4.27.6. Affected is the function et_builder_sanitize_dynamic_content_fields/et_builder_filter_resolve_default_dynamic_content of the component Dynamic Content feature. Performing a manipulation of the argument enable_html results in cross site scripting. This vulnerability is identified as CVE-2026-3851. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Elegant mes Divi Plugin up to 4.27.6. This affects the function et_builder_sanitize_dynamic_content_fields/et_builder_filter_resolve_default_dynamic_content of the component Dynamic Content feature. The manipulation of the argument enable_html with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:

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.

The advisory is shared at wordfence.com. This vulnerability is uniquely identified as CVE-2026-3851 since 03/09/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• Elegant mes

Name

• Divi Plugin

Version

• 4.27.0
• 4.27.1
• 4.27.2
• 4.27.3
• 4.27.4
• 4.27.5
• 4.27.6

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion