Avada <= 7.11.6 - Authenticated (Contributor+) Server-Side Request Forgery via form_to_url_action
Strategic Overview
- Status
- Patched in 7.11.7
- Affected Theme
- Avada | Website Builder For WordPress & WooCommerce
- Affected Version
<= 7.11.6- CVSS
- 6.4Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2024-2343
At a glance
CVE-2024-2343 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Avada WordPress theme, affecting versions <= 7.11.6. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 7.11.7; sites on affected versions should update now. Disclosed March 2024, reported by Muhammad Zeeshan (Xib3rR4dAr).
Vulnerability Overview
The Avada | Website Builder For WordPress & WooCommerce theme for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 7.11.6 via the form_to_url_action function. 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 and can be used to query and modify information from internal services.
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)
Reaching this weakness in Avada <= 7.11.6 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 Avada the fix is 7.11.7: builds <= 7.11.6 are affected, anything from 7.11.7 onward is not.
Remediation
Update to version 7.11.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: Avada 7.11.7 closes this, and updating the theme is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Avada | Website Builder For WordPress & WooCommerce
- 9.8CVE-2026-18431: Avada and Fusion Builder <= 3.16 - Unauthenticated RCE
CVE-2026-18431 - 8.8CVE-2024-1468: Avada Arbitrary File Upload
CVE-2024-1468 - 8.8CVE-2023-39312: Avada <= 7.11.1 Arbitrary File Upload
CVE-2023-39312 - 8.8CVE-2022-41996: Avada <= 7.8.1 Cross-Site Request Forgery
CVE-2022-41996 - 8.8CVE-2017-18607: Avada <= 5.1.4 Cross-Site Request Forgery
CVE-2017-18607 - 7.5CVE-2026-12256: Avada <= 3.15.3 PHP Object Injection
CVE-2026-12256 - 7.5CVE-2023-39307: Avada <= 7.11.1 Arbitrary File Upload
CVE-2023-39307 - 7.3CVE-2024-13346: Avada Theme <= 7.11.13 Arbitrary Shortcode Execution
CVE-2024-13346
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C