Divi <= 4.27.6 - Authenticated (Contributor+) Server-Side Request Forgery via 'image_src' Parameter
Strategic Overview
- Status
- Patched in 4.27.7
- Affected Theme
- Divi
- Affected Version
<= 4.27.6- CVSS
- 5.0Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2026-4361
At a glance
CVE-2026-4361 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Divi WordPress theme, affecting versions <= 4.27.6. It carries a CVSS score of 5.0 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.27.7; sites on affected versions should update now. Disclosed September 2026, reported by Osvaldo Noe Gonzalez Del Rio (Os).
Vulnerability Overview
The Divi theme for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 4.27.6. This is due to the `et_pb_set_video_oembed_thumbnail_resolution()` function using `wp_remote_get()` instead of `wp_safe_remote_get()` to fetch a remote image URL, which does not restrict requests to private or reserved IP ranges. This makes it possible for authenticated attackers, with Contributor-level access and above, to make web requests to arbitrary locations originating from the web application server. The response body is not returned to the attacker (blind SSRF), but two oracles exist: a status oracle (the returned URL string differs depending on whether the target responded with HTTP 200) and a timing oracle (response time varies by target reachability).
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.
CWE-918: Server-Side Request Forgery (SSRF)
Divi <= 4.27.6 carries this weakness at et_pb_set_video_oembed_thumbnail_resolution(), and reaching it takes an account at Contributor level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Divi the fix is 4.27.7: builds <= 4.27.6 are affected, anything from 4.27.7 onward is not.
Remediation
Update to version 4.27.7, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Divi 4.27.7 closes this, and updating the theme is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Divi
- 8.8CVE-2020-35945: Elegant Themes Arbitrary File Upload
CVE-2020-35945 - 8.8Elegant Themes Divi 3.23… , Divi Extra 2.23 - 4.0.9, Divi Builder
- 6.4CVE-2026-3853: Divi <= 4.27.6 DOM-Based Stored Cross-Site Scripting
CVE-2026-3853 - 6.4CVE-2026-3852: Divi <= 4.27.6 Stored Cross-Site Scripting
CVE-2026-3852 - 6.4CVE-2026-3850: Divi <= 4.27.6 Stored Cross-Site Scripting
CVE-2026-3850 - 6.4CVE-2026-3851: Divi <= 4.27.6 Stored Cross-Site Scripting
CVE-2026-3851 - 6.4CVE-2026-13712: Divi <= 5.8.1 Stored Cross-Site Scripting
CVE-2026-13712 - 6.4CVE-2024-5647: Multiple Plugins <= Stored DOM-Based XSS
CVE-2024-5647
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C