Elegant Themes Divi 3.23 - 4.0.9, Divi Extra 2.23 - 4.0.9, Divi Builder 2.23 - 4.0.9 - PHP Code Injection

Strategic Overview

Status
Patched in 4.0.10
Affected Theme
Divi
Affected Version
3.23 – 4.0.9
CVSS
8.8High
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE pending
View all Divi vulnerabilities

At a glance

This record tracks a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Divi WordPress theme, affecting versions 3.23 – 4.0.9. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 4.0.10; sites on affected versions should update now. Disclosed January 2020, reported by Elegant Themes Security Team.

Vulnerability Overview

The Divi Builder, Divi, and Divi Extra plugin and themes for WordPress are vulnerable to PHP Code Injection in versions up to 4.0.10. This allows authenticated attackers to execute code on a vulnerable site's server that could be used to completely take over the site.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in Divi 3.23 – 4.0.9 takes a caller who can reach the endpoint. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Divi the fix is 4.0.10: builds 3.23 – 4.0.9 are affected, anything from 4.0.10 onward is not.

Remediation

Update to version 4.0.10, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Divi: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Divi 4.0.10 closes this, and updating the theme is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C