# CVE-2026-91707: is Divi 4 affected? Divi 5 vs Divi 4

> CVE-2026-91707 affects Divi up to 5.11.1. What the record says about Divi 4 and Divi 5, how to read your version, and what to ask Elegant Themes this week.

Canonical: https://red.run.cloud/learn/divi-5-vs-divi-4-cve-2026-91707 · By Timothy Lindblom · Published 2026-11-04 · Updated 2026-11-04

CVE-2026-91707 is a medium-severity flaw in the Divi theme that lets an unauthenticated visitor run shortcodes. The CVE record lists Divi versions 0 through 5.11.1, so a Divi 4 number sits inside the range on paper, and no vendor page we could open states a Divi 4 fix. Check your theme version today and update to the newest Divi release.

| Fact | Detail | Source |
|---|---|---|
| CVE id | CVE-2026-91707, weakness CWE-862 (missing authorization) | [CVE record](https://www.cve.org/CVERecord?id=CVE-2026-91707) |
| Product | Divi theme by Elegant Themes. The record names no other Elegant Themes product | CVE record |
| Affected versions | 0 through 5.11.1 (semver range) | CVE record, [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-91707) |
| Fix reference | The record's only vendor reference is the [Divi 5.12.0 changelog entry](https://www.divichangelog.com/divi-update/divi-5/version-5-12-0). GitHub lists patched versions as unknown | CVE record, [GitHub advisory](https://github.com/advisories/GHSA-8xr3-mxv3-qm4h) |
| Severity | CVSS v3.1 5.3, Medium. Vector: network, no privileges, integrity low | NVD, [FIRST spec](https://www.first.org/cvss/v3.1/specification-document) |
| Published | 18 September 2026 (NVD and GitHub) | NVD |
| Finder | Osvaldo Noe Gonzalez Del Rio (Os), credited in the record | CVE record |
| Exploitation | Not in CISA's catalog at version 2026.10.30. No exploitation report found | [CISA](https://www.cisa.gov/known-exploited-vulnerabilities-catalog) |
| Checked | 4 November 2026 | this page |

## Is Divi 4 affected by CVE-2026-91707?

On the face of the record, yes. The record has one product, Divi, with one affected range: version 0 through 5.11.1. It does not split Divi 4 from Divi 5. Any 4.x number is lower than 5.11.1, so a site on Divi 4 is inside the range as written.

What the record does not say matters just as much. It names no fixed Divi 4 release, and it does not say Divi 4 lacks the vulnerable code path. The vendor's own pages that the record cites (the changelog and the 5.12.0 entry) returned HTTP 403 when we tried them on 24 October and again on 4 November 2026, so we could not read what Elegant Themes says about Divi 4.

That leaves three honest readings, and the record cannot choose between them:

1. Divi 4 has the same flaw and the vendor ships a fix for it.
2. Divi 4 has the same flaw and the vendor has not said how it will be fixed.
3. Divi 4 is outside the vulnerable code path, and the range is simply written loosely.

Until Elegant Themes states which one is true for your version, treat Divi 4 as in scope and ask for a written answer (the questions are below).

## Why do owners keep asking about Divi 4 versus Divi 5?

Because the name carries two generations and the record carries one range. Divi 5 is the newer builder. The theme that runs on your site reports a single version number, and the CVE ranges over that number.

The advisory adds a condition that sounds specific to one generation. Its text says that when the "Force Enable D4 Shortcode Framework" option is enabled, the contact form shortcode can be used to send email to an attacker-selected recipient. The name of that option points at compatibility with the older Divi 4 shortcode system. The record does not say where the option lives, what it is set to by default, or whether Divi 4 sites have an equivalent. We will not guess at those.

What the description does state is wider than the contact form. The flaw is that an action does not validate a value before calling `do_shortcode`, so a visitor can make the site run arbitrary shortcodes. The contact form email is the example the advisory spells out for sites with that option on.

## Which version do I have, and what does the record say about it?

| What you see | Inside the record's range? | What the record leaves open | What to do |
|---|---|---|---|
| Divi 5.11.1 or lower in 5.x | Yes | Nothing for 5.x: this is the named range | Update to the newest Divi release. Read the 5.12.0 entry |
| Divi 4.x (any number) | Yes, numerically | Whether a fixed 4.x release exists | Ask Elegant Themes for the answer for your exact number. Update to the newest Divi 4 release meanwhile |
| A child theme of Divi | Judge by the parent Divi version | Nothing extra. The child inherits parent code | Read the parent theme's version, update the parent |
| Divi Builder plugin or Extra theme | Not named | Whether they share the code | Ask in writing. Update them as well |
| A version above 5.11.1 | Outside the named range | Whether it includes the fix | Confirm in the changelog that the release addresses the CVE |

<figure class="ln-figure">
<svg viewBox="0 0 720 230" role="img" aria-labelledby="ln-divi-title" xmlns="http://www.w3.org/2000/svg" font-family="Geist, sans-serif">
<title id="ln-divi-title">Divi version line: the CVE-2026-91707 range runs from 0 through 5.11.1; 5.12.0 is the vendor reference</title>
<rect x="0" y="0" width="720" height="230" fill="#FFFFFF"/>
<text x="24" y="34" font-size="15" fill="#1A0F0F">Divi version number, left to right</text>
<line x1="40" y1="120" x2="680" y2="120" stroke="#1A0F0F" stroke-width="2"/>
<rect x="40" y="96" width="470" height="48" fill="#FFF1EF" stroke="#C70500" stroke-width="2"/>
<text x="56" y="126" font-size="14" fill="#B00500">Range in the CVE record: 0 through 5.11.1</text>
<rect x="40" y="152" width="170" height="30" fill="#EAD3CF"/>
<text x="52" y="172" font-size="13" fill="#1A0F0F">Divi 4.x numbers</text>
<rect x="222" y="152" width="288" height="30" fill="#EAD3CF"/>
<text x="234" y="172" font-size="13" fill="#1A0F0F">Divi 5.x up to 5.11.1</text>
<line x1="510" y1="80" x2="510" y2="150" stroke="#C70500" stroke-width="2"/>
<text x="470" y="72" font-size="13" fill="#1A0F0F">5.11.1</text>
<line x1="590" y1="90" x2="590" y2="150" stroke="#655553" stroke-width="2" stroke-dasharray="5 4"/>
<text x="560" y="82" font-size="13" fill="#1A0F0F">5.12.0</text>
<text x="528" y="198" font-size="12" fill="#655553">Vendor entry cited by the record</text>
<text x="40" y="214" font-size="12" fill="#655553">Divi 4 sits inside the range on paper. No vendor statement on a Divi 4 fix was readable on 4 November 2026.</text>
</svg>
<figcaption>The record is one range for one product name. Where Divi 4 falls inside it is a matter of arithmetic, which is why a written vendor answer matters.</figcaption>
</figure>

## How do I find my Divi version?

In the WordPress admin, go to Appearance, then Themes, and select Divi. The details panel shows the version. Site Health under Tools, on the Info tab, also lists the active theme and its version, and the parent theme if you use a child theme.

If you cannot log in, a developer can read the `Version:` line at the top of the theme's `style.css`. Do not read the version from a page builder label or from a design file name, because those can show the builder generation and not the theme release.

Write down three things before changing anything: the version number, whether a child theme is active, and whether a caching layer sits in front of the site. Those answers decide the rest.

## What can a visitor actually do through it?

The advisory describes missing authorization (CWE-862). In plain terms, an action on the site takes a value from a request and hands it to WordPress's shortcode runner without checking who is asking or whether the value is allowed. WordPress's own [`do_shortcode` reference](https://developer.wordpress.org/reference/functions/do_shortcode/) describes a function that finds shortcodes in content and runs them. The reference lists no capability check inside it, and the [Shortcode API handbook](https://developer.wordpress.org/apis/shortcode/) leaves permission checks to the code that calls it. That is the gap the advisory describes.

The only concrete consequence the advisory spells out is the contact form email, and only when the "Force Enable D4 Shortcode Framework" option is on. Beyond that, the reach of "arbitrary shortcodes" depends on which shortcodes your site has registered. That is our reading of the wording, not a statement from the record, so treat it as a reason to look at the shortcodes your plugins add.

The score fits that picture. [FIRST's CVSS v3.1 specification](https://www.first.org/cvss/v3.1/specification-document) puts Medium at 4.0 to 6.9. The vector in the [NVD entry](https://nvd.nist.gov/vuln/detail/CVE-2026-91707) says network reachable, no privileges, integrity impact low, and no confidentiality or availability impact.

## How do I fix it?

### If you run the WordPress site yourself

- [ ] Take a backup, then note the current Divi version and any child theme.
- [ ] Update the Divi theme to the newest release available to your licence. Elegant Themes publishes release notes in its [changelog](https://www.divichangelog.com/); read the 5.12.0 entry, which is the one the record cites.
- [ ] Purge the site cache and any CDN cache after updating, then reload a page and confirm the theme version again.
- [ ] If you run Divi 4, ask Elegant Themes the question below before assuming the update closes this CVE.
- [ ] Update the Divi Builder plugin and Extra if you use them.
- [ ] Look at the Force Enable D4 Shortcode Framework option and write down whether it is on. Switch it off only if nothing on your site relies on older shortcodes, and test the site afterwards.

### If an agency or host manages the site

Send this and keep the reply:

> For **[your domain]**, which Divi version is installed (theme and child theme), and is it newer than 5.11.1? Please confirm the date it was updated and that caches were cleared. If we run Divi 4, please give the release that addresses CVE-2026-91707 or Elegant Themes' written statement that Divi 4 is not affected.

Managed hosts that patch automatically usually patch software they run, such as PHP and WordPress core. A premium theme is often outside that. For who owns that job, see [who owns patching a theme like this](/learn/who-is-responsible-for-patching-my-website), and for how hosts handle plugin and theme flaws at the firewall level, see [managed WordPress hosts compared on virtual patching](/learn/managed-wordpress-hosts-virtual-patching-compared). A host rule that blocks a request pattern is a stopgap. It does not change the theme version. Some vendors also keep [remote-control keys on your site](/learn/which-plugins-hold-remote-control-keys), which is worth knowing when you ask who can touch it.

### What to ask Elegant Themes

> We run Divi **[version]** on **[domain]**. CVE-2026-91707 lists Divi 0 through 5.11.1. Is Divi 4.x affected? If yes, which release fixes it? Does the Force Enable D4 Shortcode Framework option exist in our version, and what is its default? Are the Divi Builder plugin and Extra affected?

## Am I affected? A three-state self-test

<div class="ln-selftest">
<h3>Am I affected? Where you stand right now</h3>
<p>A check from outside can read what your site serves. It cannot see the theme file on your server, a child theme's parent, the state of the option above, or whether caches were purged.</p>
<ol>
<li><span class="ln-state ln-state-detected">Detected</span> <strong>Your site serves Divi and the version it shows is 5.11.1 or lower, which includes any 4.x number.</strong> Treat it as in scope. Update the theme, or ask the person who manages it today.</li>
<li><span class="ln-state ln-state-unknown">Unknown</span> <strong>The Divi version is hidden, a child theme or caching layer hides the parent, or you run Divi 4 with no vendor statement.</strong> This is the common case. Read the version in the admin and get the vendor's written answer for Divi 4.</li>
<li><span class="ln-state ln-state-confirmed">Confirmed by owner evidence</span> <strong>You can show the parent theme's version in the admin or in <code>style.css</code> on the server, a Divi changelog entry that addresses this CVE for that release, and a cache purge after the update.</strong> The theme is on a release the vendor lists as fixed. Whether anyone abused it before then is a separate question.</li>
</ol>
<p>No scan, ours included, moves you from "unknown" to "confirmed".</p>
</div>

## Was CVE-2026-91707 exploited?

We found no primary source reporting exploitation. At our check on 4 November 2026 the CVE was not in [CISA's Known Exploited Vulnerabilities catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog) (version 2026.10.30). We could not open the Wordfence record the CVE cites, so we cannot say what it reports.

Absence from a list is not evidence that nobody tried it. If your site was on a version at or below 5.11.1 for a while, look at what the contact form could have sent. Check the outgoing mail log or the mailbox that receives form notifications for messages nobody on your team wrote, and ask your mail provider whether it saw unusual volume from your domain. Unexpected spam from your own domain can also hurt its reputation with mailbox providers.

If you find something, the [step-by-step incident response guide](/learn/website-incident-response-playbook) covers what to do next, and [finding a hidden WordPress admin](/learn/find-a-hidden-wordpress-admin) helps if an account you do not recognise appeared. For other WordPress flaws from October, the [running list of October incidents](/learn/october-2026-security-meltdown-tracker) lists them, including the [Bricksforge flaw](/learn/bricksforge-cve-2026-85097-rce) and the [Ninja Forms issue](/learn/ninja-forms-wpc-xss-hidden-admins). Other plugin bugs with a similar shape are the [Elementor Pro upload-field flaw](/learn/elementor-pro-cve-2026-32475-upload-field) and the [GiveWP card-testing hole](/learn/givewp-rce-cve-2026-82222-card-testing), and [the other WordPress guides](/learn/topics/wordpress) cover the rest.

## What can the free scan tell me about Divi?

The free scan reads the stack your site serves and matches each version to known vulnerabilities. It is a lookup: it can say a version is affected, not whether your setup is exposed. If Divi shows a version from outside, a match to a CVE record is a "detected" result. If the version is hidden, the result is "unknown", and only your admin screen or your host can settle it.

It cannot tell you whether the Force Enable D4 Shortcode Framework option is on, whether Elegant Themes has a Divi 4 fix, or whether anything was abused. [What an external website scan cannot prove](/learn/what-an-external-website-scan-cant-prove) lists the limits of any outside check.

## What we could not confirm

Elegant Themes' own changelog pages returned HTTP 403 to us on 24 October and again on 4 November 2026, and we did not read the Wordfence record or any Patchstack entry. So this page does not state the fixed Divi 5 release as a confirmed fact beyond "the record points to the 5.12.0 entry", does not give any Divi 4 version numbers, and does not say whether Divi 4 receives the fix. When a vendor page is readable we will update this page and say what changed.

## Questions people ask

### Is Divi 4 affected by CVE-2026-91707?

The CVE record lists Divi as affected from version 0 through 5.11.1. A Divi 4 version number is lower than 5.11.1, so it falls inside that range on paper. We found no vendor statement that clears Divi 4 or names a Divi 4 fix. Ask Elegant Themes for a written answer for your exact version.

### I am on Divi 5.11.1. Am I affected?

Yes, by the record. 5.11.1 is the last affected version it names. The CVE record points to the Divi 5.12.0 changelog entry as the vendor reference, so update to the newest Divi release and read that entry to confirm it lists the fix.

### What can an attacker do through this flaw?

The advisory says an unauthenticated visitor can make the site run shortcodes of their choosing. When the Force Enable D4 Shortcode Framework option is on, the contact form shortcode can send email to a recipient and with content the visitor picks. The CVSS score of 5.3 reflects limited integrity impact and no confidentiality or availability impact.

### How do I check which Divi version my site runs?

In the WordPress admin open Appearance, then Themes, and select Divi to read its version. If you use a child theme, the number that matters is the parent Divi theme, not the child. Site Health under Tools also lists the active theme and parent theme with versions.

### Does updating the Divi Builder plugin or Extra fix this?

The record names the Divi theme only. It says nothing about the Divi Builder plugin or the Extra theme, so we cannot say either is affected or cleared. Ask Elegant Themes in writing, and update every Elegant Themes product you run.

### Is CVE-2026-91707 being exploited?

We found no primary source reporting exploitation. CISA's catalog of known exploited vulnerabilities did not list it at our 4 November 2026 check, and we could not open the Wordfence record. Absence from that list is not proof that nobody tried it, so update anyway.


## Sources

1. [CVE-2026-91707 record (CVE Program, assigned by Wordfence)](https://www.cve.org/CVERecord?id=CVE-2026-91707): Vendor Elegant Themes, product Divi, affected versions 0 through 5.11.1, finder credit, three references. Read from the CVE JSON record on 4 November 2026; last updated 18 September 2026.
2. [NVD: CVE-2026-91707](https://nvd.nist.gov/vuln/detail/CVE-2026-91707): Published 18 September 2026, CVSS v3.1 5.3 Medium, CWE-862. Read through the NVD API on 24 October 2026.
3. [GitHub Advisory GHSA-8xr3-mxv3-qm4h](https://github.com/advisories/GHSA-8xr3-mxv3-qm4h): Full description, including the Force Enable D4 Shortcode Framework condition. Lists patched versions as unknown. Checked 4 November 2026.
4. [Wordfence vulnerability record for Divi (cited by the CVE record)](https://www.wordfence.com/threat-intel/vulnerabilities/id/79a2fa3b-f9eb-49d8-97be-3a81d1b69c2e): Returned an empty page to our fetch on 4 November 2026. Cited because the CVE record names it; we did not read it.
5. [Divi changelog (cited by the CVE record)](https://www.divichangelog.com/): Returned HTTP 403 to our fetch on 24 October and 4 November 2026. Where the vendor's release notes live.
6. [Divi 5.12.0 changelog entry (cited by the CVE record)](https://www.divichangelog.com/divi-update/divi-5/version-5-12-0): The only vendor page the CVE record points to. Returned HTTP 403 to our fetch on 24 October and 4 November 2026.
7. [CISA Known Exploited Vulnerabilities catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog): CVE-2026-91707 was not in catalog version 2026.10.30 (released 30 October 2026) at our 4 November check.
8. [WordPress developer reference: do_shortcode()](https://developer.wordpress.org/reference/functions/do_shortcode/): Describes the function the advisory names. The reference lists no capability check inside it.
9. [WordPress Shortcode API handbook](https://developer.wordpress.org/apis/shortcode/): What a shortcode is and how a handler is registered.
10. [FIRST: CVSS v3.1 specification](https://www.first.org/cvss/v3.1/specification-document): Defines the Medium band (4.0 to 6.9) and the vector terms used in the record.
11. [Elegant Themes help center: Divi 5 collections](https://help.elegantthemes.com/en/collections/10650977-divi-5): Vendor documentation hub for Divi 5. It lists a Divi 5 FAQ and a separate Divi 4 collection; we found no page on this CVE there.
