Divi vulnerabilities

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 allows authenticated attackers with Contributor-level access and above to make web requests to arbitrary locations from the web application server. The response body is not returned (blind SSRF), but status and timing oracles exist.

The Divi theme for WordPress is vulnerable to DOM-Based Stored Cross-Site Scripting via the `image_src` attribute of the `et_pb_video_slider_item` shortcode in all versions up to and including 4.27.6. This is due to the `image_src` field not being included in the `$url_options` whitelist, so it never receives `esc_url_raw()` at save time. On the server side, the value is rendered into a `data-image` HTML attribute using `esc_attr()`, but the client-side JavaScript reads this attribute using jQuery's `.data('image')`, which returns the browser-decoded value, which is then concatenated into an HTML string and injected into the DOM without re-escaping. This allows authenticated attackers with Contributor-level access and above to inject arbitrary web scripts that execute when a user hovers over the carousel thumbnail.

The Divi WordPress theme before version 5.9.0 does not properly escape some Social Media Follow module settings before outputting them in link attributes, allowing users with contributor role or above to store JavaScript that executes when a higher-privileged user, such as an admin, views the post.