CVE-2026-3851
Received Received - Intake

Stored XSS in Divi Theme via Dynamic Content Feature

Publication date: 2026-09-02

Last updated on: 2026-09-02

Assigner: Wordfence

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-02
Last Modified
2026-09-02
Generated
2026-09-02
AI Q&A
2026-09-02
EPSS Evaluated
N/A
NVD
CVE-2026-3851
EUVD
EUVD-2026-69830

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
elegantthemes divi to 4.27.6 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
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.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Stored Cross-Site Scripting (XSS) vulnerability in the Divi WordPress theme affecting versions up to 4.27.6. It occurs via the Dynamic Content feature's legacy JSON format. The vulnerability bypasses save-time sanitization filters because the rendering engine silently converts legacy JSON format to a different format at render time, avoiding the filter. Additionally, a resolver does not properly sanitize HTML output when enabled, allowing raw post meta values to be injected into pages.

Impact Analysis

Authenticated attackers with Contributor-level access or higher can inject malicious scripts into pages. When users access these pages, the injected scripts execute in their browsers. This could lead to theft of session cookies, account takeover, or defacement of the website. The impact depends on user privileges and site configuration.

Mitigation Strategies
  • Update the Divi theme to version 4.27.7 or later to address the stored XSS and legacy Dynamic Content JSON issues.
  • Review user roles with Contributor-level access or higher to ensure they are trusted, as they can exploit this vulnerability.
  • Monitor for unusual script injections in pages using the Dynamic Content feature, especially those using legacy JSON format.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-3851. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart