PatchSiren cyber security CVE debrief
CVE-2026-3850 Elegant Themes CVE debrief
The Divi theme for WordPress has a Stored Cross-Site Scripting vulnerability via the `redirect_url` parameter of the `et_pb_contact_form` shortcode. This issue allows authenticated attackers with Contributor-level access and above to inject arbitrary web scripts, potentially leading to security breaches and data exposure. The vulnerability exists due to improper sanitization of the `redirect_url` attribute, which is sanitized with `esc_attr()` instead of `esc_url()`. Additionally, the `redirect_url` parameter is not included in the `$url_options` array for `esc_url_raw()` sanitization during shortcode parsing.
- Vendor
- Elegant Themes
- Product
- Divi
- CVSS
- MEDIUM 6.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-02
- Original CVE updated
- 2026-09-04
- Advisory published
- 2026-09-02
- Advisory updated
- 2026-09-04
Who should care
WordPress administrators and users with Contributor-level access and above should assess exposure and prioritize remediation. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
Why it matters
CVE-2026-3850 allows authenticated attackers to inject arbitrary web scripts, potentially leading to security breaches and data exposure.
- Authenticated attackers can inject arbitrary web scripts
- Scripts execute when a user submits the contact form
- Client-side JavaScript reads the `data-redirect_url` attribute and passes it to `window.location.href`
Technical summary
The Divi theme for WordPress is vulnerable to Stored Cross-Site Scripting via the `redirect_url` parameter of the `et_pb_contact_form` shortcode in all versions up to, and including, 4.27.6. This is due to the `redirect_url` attribute being sanitized with `esc_attr()` instead of `esc_url()` before being rendered into the `data-redirect_url` HTML data attribute. Additionally, `redirect_url` is absent from the hardcoded `$url_options` array in `class-et-builder-element.php`, so it does not receive `esc_url_raw()` sanitization during shortcode parsing.
Defensive priority
Medium
Recommended defensive actions
- Update the Divi theme to the latest version
- Restrict access to the contact form to prevent unauthorized submissions
- Monitor for suspicious activity on the contact form
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The vulnerability exists due to improper sanitization of the `redirect_url` attribute. The `redirect_url` parameter is sanitized with `esc_attr()` instead of `esc_url()` and is not included in the `$url_options` array for `esc_url_raw()` sanitization during shortcode parsing. This allows authenticated attackers to inject arbitrary web scripts, which can be executed when a user submits the contact form.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-3850 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-3850
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-3850 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-3850
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.divichangelog.com/divi-update
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.