CVE-2026-3851
Last modified
CVE-2026-3851 is a medium-severity vulnerability rated 6.4/10 on the CVSS scale. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Elegant Themes | Divi | <= 4.27.6 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-3851?
How severe is CVE-2026-3851?
How do I fix CVE-2026-3851?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-38473A Stored XSS vulnerability in the subtitle deletion flow in …5.4
- CVE-2026-38474GazellePW (GazellePosterWall) commit 86c4bedf727691b5a97af42…5.4
- CVE-2026-3848GitLab has remediated an issue in GitLab CE/EE affecting all…5
- CVE-2026-3849Stack Buffer Overflow in wc_HpkeLabeledExtract via Oversized…9.8
- CVE-2026-3850The Divi theme for WordPress is vulnerable to Stored Cross-S…6.4
- CVE-2026-38500Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2026-3852The Divi theme for WordPress is vulnerable to Stored Cross-S…6.4
- CVE-2026-38526An authenticated arbitrary file upload vulnerability in the …9.9
- CVE-2026-38527A Server-Side Request Forgery (SSRF) in the /settings/webhoo…8.5
- CVE-2026-38528Krayin CRM v2.2.x was discovered to contain a SQL injection …7.1
- CVE-2026-38529A Broken Object-Level Authorization (BOLA) in the /Settings/…8.8
- CVE-2026-3853The Divi theme for WordPress is vulnerable to DOM-Based Stor…6.4
Are you affected by CVE-2026-3851?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
