# CVE-2026-3851: Elegant Themes Divi stored cross-site scripting in Dynamic Content

Source: https://junglewise.ai/threats/cve-2026-3851-elegant-themes-divi-stored-cross-site-scripting-in-dynamic-content  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-02. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-3851 · Severity: medium · CVSS 6.4 · Published 2026-09-02

The Divi theme, a popular WordPress page builder and design tool, contains a stored cross-site scripting vulnerability in its Dynamic Content feature. Attackers with Contributor-level access can inject malicious scripts that execute whenever site visitors view affected pages, potentially stealing credentials, session tokens, or sensitive data. This impacts the security of any WordPress site using Divi up to version 4.27.6.

Technologies: [Elegant Themes Divi](https://junglewise.ai/threats/technologies/divi). Vendors: [Elegant Themes](https://junglewise.ai/threats/vendors/elegant-themes).

## Quick answers

**Is CVE-2026-3851 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-3851 being exploited in the wild.

**How severe is CVE-2026-3851?** Medium severity, with a CVSS score of 6.4, published 2 September 2026.

**Which products and versions are affected?** Elegant Themes Divi up to 4.27.6.

**Is there a fix for CVE-2026-3851?** A patch was published on 2026-09-02: Fixed in version 4.27.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-3851 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-3851?** Check whether you run Elegant Themes Divi at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability stems from two compounding flaws in the Dynamic Content feature: (1) the save-time sanitization filter only checks for the standard `@ET-DC@...@` format, but the rendering engine also supports a legacy JSON format that bypasses this filter at render time, and (2) the `post_meta_key` resolver fails to apply `wp_kses_post()` sanitization when `enable_html` is enabled, passing raw post metadata directly to output. An authenticated attacker with Contributor-level or higher permissions can exploit this to inject persistent XSS payloads. The vulnerability is fixed in version 4.27.7 and later.

## Affected products

- Elegant Themes Divi up to 4.27.6

## Timeline

- 2026-09-02: disclosed
- 2026-09-02: patched: Fixed in version 4.27.7

## References

- [https://www.divichangelog.com/divi-update/divi-4/version-4-27-7](https://www.divichangelog.com/divi-update/divi-4/version-4-27-7)
- [https://www.wordfence.com/threat-intel/vulnerabilities/id/9384d32d-77a1-4794-aace-96f553302a3b?source=cve](https://www.wordfence.com/threat-intel/vulnerabilities/id/9384d32d-77a1-4794-aace-96f553302a3b?source=cve)

## Related threats

- [Elegant Themes Divi arbitrary shortcode execution](https://junglewise.ai/threats/cve-2026-91707-elegant-themes-divi-arbitrary-shortcode-execution)
- [Elegant Themes Divi server-side request forgery in video thumbnail function](https://junglewise.ai/threats/cve-2026-4361-elegant-themes-divi-server-side-request-forgery-in-video-thumbnail)
- [Elegant Themes Divi DOM-based stored XSS in video slider](https://junglewise.ai/threats/cve-2026-3853-elegant-themes-divi-dom-based-stored-xss-in-video-slider)
- [Elegant Themes Divi stored XSS in Social Media Follow shortcode](https://junglewise.ai/threats/cve-2026-3852-elegant-themes-divi-stored-xss-in-social-media-follow-shortcode)
- [Elegant Themes Divi stored cross-site scripting in contact form](https://junglewise.ai/threats/cve-2026-3850-elegant-themes-divi-stored-cross-site-scripting-in-contact-form)