GHSA-Q2Q3-CP6P-R7MV
Vulnerability from github – Published: 2026-09-02 09:31 – Updated: 2026-09-02 09:31The 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.
{
"affected": [],
"aliases": [
"CVE-2026-3850"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-02T07:16:36Z",
"severity": "MODERATE"
},
"details": "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.",
"id": "GHSA-q2q3-cp6p-r7mv",
"modified": "2026-09-02T09:31:29Z",
"published": "2026-09-02T09:31:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-3850"
},
{
"type": "WEB",
"url": "https://www.divichangelog.com/divi-update"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/768fb279-8d35-4002-91d8-c6a3b0f8f51d?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.