{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-4361 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4361 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4361 is a medium-severity server-side request forgery vulnerability in Elegant Themes Divi, published on 5 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-4361 and fix it if it is affected.\n\nWhat it is: CVE-2026-4361 is a medium-severity server-side request forgery vulnerability in Elegant Themes Divi, published on 5 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-4361 in the wild and no public exploit code.\n\nAffected product: Elegant Themes Divi. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-4361/ (Markdown: https://insights.sbomify.com/CVE-2026-4361/index.md)","id":"CVE-2026-4361","markdown":"https://insights.sbomify.com/CVE-2026-4361/index.md","name":"CVE-2026-4361","record":{"aliases":["GHSA-pjxf-f8rh-3cjp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass","other"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress theme","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit a Server-Side Request Forgery vulnerability in the Divi theme to make arbitrary web requests from the server.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Divi \u003c= 4.27.6 - Authenticated (Contributor+) Server-Side Request Forgery via 'image_src' Parameter","id":"CVE-2026-4361","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"ElementsKit Elementor Addons \u003c= 3.8.2 - Missing Authorization to Unauthenticated Widget Content Overwrite","id":"CVE-2026-4362"},"packages":[],"prev":{"headline":"Tarfile.extract() doesn't fully respect filter parameter","id":"CVE-2026-4360"},"products":["Divi"],"published":"2026-09-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-07","vendors":["Elegant Themes"]},"summary":"Authenticated attackers can exploit a Server-Side Request Forgery vulnerability in the Divi theme to make arbitrary web requests from the server.","url":"https://insights.sbomify.com/CVE-2026-4361/"}