Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker registers or compromises a Contributor-level WordPress account
-
DeliveryEdits a page to embed `et_pb_contact_form` with `javascript:` URI in `redirect_url`
-
ExploitPage saved; `esc_attr()` fails to strip URI scheme, value stored in `data-redirect_url` attribute
-
ExecutionVictim visits page and submits contact form
-
PersistClient-side JavaScript reads attribute and assigns to `window.location.href`
-
ImpactArbitrary script executes in victim's browser session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to hold at minimum Contributor-level access to the target WordPress installation - this role must be explicitly granted by a site administrator and is not available to anonymous visitors or Subscriber-role accounts. The attacker must also be able to create or edit a page or post that embeds the |
| Impact | The CVSS 6.4 score appropriately reflects the Contributor access requirement (PR:L), which narrows the attacker pool to registered WordPress users granted that role or higher - not arbitrary internet actors. The scope-change metric (S:C) is correctly applied because the payload executes in victims' browsers rather than the attacker's context. However, the provided vector uses UI:N, which is inconsistent with the attack mechanics: a victim must actively submit the contact form containing the poisoned shortcode for the payload to fire, making UI:R the more precise metric and reducing the realistic base score to approximately 5.4. No EPSS data was supplied, and the vulnerability is absent from CISA KEV with no public exploit code identified - exploitation probability at time of analysis is inferred to be low. Despite the elevated access requirement, Divi's millions of active installations create substantial aggregate exposure; sites that permit untrusted or semi-trusted users to edit pages should prioritize patching. The CVSS conflict between UI:N (provided) and the form-submission trigger (described) should be verified with the vendor before treating the 6.4 score as authoritative. |
| Exploit ScenarioDerived | An attacker who has obtained or registered a Contributor-level account on a target WordPress site running Divi through 4.27.6 edits a page to include an |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 02, 2026
Stored Cross-Site Scripting in Elegant Themes' Divi WordPress theme (all versions through 4.27.6) enables authenticated contributors to plant a javascript: URI in the redirect_url parameter of the et_pb_contact_form shortcode, which executes in any visitor's browser upon contact form submission. The flaw arises from using esc_attr() instead of esc_url() for sanitization and the parameter's absence from the $url_options URL-sanitization array, allowing the raw URI to reach client-side JavaScript that assigns it to window.location.href. No public exploit code or CISA KEV listing has been identified at time of analysis, but Divi's enormous deployment footprint makes this a meaningful aggregate risk despite the Contributor access prerequisite.
RemediationAI
The primary fix is to update Divi to the first version released after 4.27.6 that addresses this issue; the Divi changelog at https://www.divichangelog.com/divi-update should be monitored for the specific patched release, as no exact fix version was confirmed in the available data. If an immediate update is not feasible, site administrators should audit which users hold Contributor role or higher and revoke that capability from any untrusted accounts, since the attack requires at minimum Contributor access to inject the payload. As a compensating control, a web application firewall rule stripping or blocking javascript: scheme values in POST parameters can prevent the URI from reaching the data attribute, though this may interfere with legitimate redirect URLs and is not a substitute for patching. Additionally, disabling or removing et_pb_contact_form shortcodes from publicly accessible pages eliminates the attack surface entirely until a patch is applied, at the cost of losing contact form functionality on those pages.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Divi is a commercial WordPress page-builder theme developed by Elegant Themes, confirmed as one of the most widely deployed premium WordPress themes globally (CPE: cpe:2.3:a:elegant_themes:divi:*:*:*:*:*:*:*:*). The vulnerability lives in the shortcode handler for et_pb_contact_form inside class-et-builder-element.php. The redirect_url shortcode attribute is passed through esc_attr(), which HTML-encodes characters such as quotes and angle brackets but does not strip javascript: URI schemes - that sanitization requires esc_url() or esc_url_raw(). Because redirect_url is also missing from the hardcoded $url_options array that would trigger esc_url_raw() during shortcode parsing, the unstripped value is emitted into the data-redirect_url HTML data attribute. Divi's client-side JavaScript reads that attribute value and unconditionally assigns it to window.location.href after a successful form submission, causing the browser to evaluate the javascript: URI and execute the attacker's payload. CWE-79 (Improper Neutralization of Input During Web Page Generation / Stored XSS) is the correct root-cause classification.
Know when Divi gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
UI:R corrects the provided UI:N because a victim must submit the contact form to trigger the stored payload; all other metrics align with the description.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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. After a successful form submission, client-side JavaScript reads this data attribute and passes it directly to window.location.href, executing arbitrary JavaScript from a javascript: URI. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that execute whenever a user submits the contact form.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Directory traversal vulnerability in the Elegant Themes Divi theme for WordPress allows remote attackers to read arbitra
Stored cross-site scripting in the Divi WordPress theme (versions 5.0 through before 5.9.0) allows any contributor-role
Stored XSS in the Divi WordPress theme's Social Media Follow module allows authenticated Contributor-level users to inje
The Divi theme for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 4.25.1 d
The Divi theme for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'et_pb_text' shortcode in all
Stored XSS in Elegant Themes' Divi WordPress theme (all versions through 4.27.6) allows authenticated attackers with Con
DOM-based stored Cross-Site Scripting in the Divi WordPress theme (all versions through 4.27.6) allows authenticated Con
Auth. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. No vendor pat
Unauthenticated arbitrary shortcode execution in the Divi theme for WordPress (all versions up to and including 5.11.1)
Blind Server-Side Request Forgery in the Divi WordPress theme (all versions through 4.27.6) allows authenticated Contrib
EUVD-2026-69886
GHSA-q2q3-cp6p-r7mv
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB