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