CVE-2025-11536: CWE-918 Server-Side Request Forgery (SSRF) in bdthemes Element Pack Addons for Elementor
The Element Pack Addons for Elementor plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 8.2.5 via the wp_ajax_import_elementor_template action. This makes it possible for authenticated attackers, with Subscriber-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.
AI Analysis
Technical Summary
CVE-2025-11536 is a Blind Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918, found in the Element Pack Addons for Elementor WordPress plugin. This plugin is widely used to extend Elementor page builder functionality. The vulnerability exists in all versions up to and including 8.2.5 and is exploitable via the wp_ajax_import_elementor_template AJAX action. An attacker with authenticated access at the Subscriber level or above can trigger this action to make the server send arbitrary HTTP requests to internal or external systems. Because the SSRF is blind, the attacker does not directly see the response but can infer information based on side effects or timing. This can be leveraged to access internal services that are otherwise inaccessible externally, potentially leading to information disclosure or further exploitation. The vulnerability requires no user interaction beyond authentication, which lowers the barrier for exploitation in environments where user registration is open or compromised accounts exist. The CVSS 3.1 base score is 5.0, reflecting network attack vector, low attack complexity, low privileges required, no user interaction, and partial confidentiality impact. No patches or public exploits are currently available, but the vulnerability's presence in a popular plugin used by many European organizations makes it a significant concern. The SSRF can be used to scan internal networks, access metadata services, or interact with internal APIs, increasing the risk of lateral movement or data leakage.
Potential Impact
For European organizations, this vulnerability poses a risk of internal network reconnaissance and potential data exposure from internal services that are normally protected by network segmentation or firewalls. Since the vulnerability requires only Subscriber-level authentication, attackers can exploit it in environments with weak user registration controls or compromised credentials. This can lead to unauthorized access to sensitive internal resources, including internal APIs, databases, or cloud metadata services, which may result in information disclosure or facilitate further attacks. The impact on confidentiality is moderate, while integrity and availability impacts are minimal. Organizations relying heavily on WordPress with Elementor and this plugin are at risk of targeted attacks aiming to pivot into internal networks. The vulnerability could also be leveraged in multi-tenant hosting environments to attack other tenants or infrastructure. Given the widespread use of WordPress and Elementor in Europe, especially in small and medium enterprises and public sector websites, the potential impact is significant if left unmitigated.
Mitigation Recommendations
1. Immediately update the Element Pack Addons for Elementor plugin to a patched version once available. 2. If no patch is available, restrict access to the wp_ajax_import_elementor_template AJAX action by implementing web application firewall (WAF) rules that block or monitor suspicious requests targeting this endpoint. 3. Limit user registration and enforce strong authentication controls to reduce the risk of attacker access with Subscriber-level privileges. 4. Employ network segmentation and internal service access controls to minimize the impact of SSRF by restricting what internal resources the web server can reach. 5. Monitor logs for unusual outbound HTTP requests originating from the web server, especially to internal IP ranges or unexpected external destinations. 6. Consider disabling or removing the plugin if it is not essential to reduce the attack surface. 7. Conduct internal security assessments to identify any potential exploitation attempts and verify the integrity of internal services. 8. Educate administrators and developers about SSRF risks and secure coding practices to prevent similar vulnerabilities.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Poland
CVE-2025-11536: CWE-918 Server-Side Request Forgery (SSRF) in bdthemes Element Pack Addons for Elementor
Description
The Element Pack Addons for Elementor plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 8.2.5 via the wp_ajax_import_elementor_template action. This makes it possible for authenticated attackers, with Subscriber-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.
AI-Powered Analysis
Technical Analysis
CVE-2025-11536 is a Blind Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918, found in the Element Pack Addons for Elementor WordPress plugin. This plugin is widely used to extend Elementor page builder functionality. The vulnerability exists in all versions up to and including 8.2.5 and is exploitable via the wp_ajax_import_elementor_template AJAX action. An attacker with authenticated access at the Subscriber level or above can trigger this action to make the server send arbitrary HTTP requests to internal or external systems. Because the SSRF is blind, the attacker does not directly see the response but can infer information based on side effects or timing. This can be leveraged to access internal services that are otherwise inaccessible externally, potentially leading to information disclosure or further exploitation. The vulnerability requires no user interaction beyond authentication, which lowers the barrier for exploitation in environments where user registration is open or compromised accounts exist. The CVSS 3.1 base score is 5.0, reflecting network attack vector, low attack complexity, low privileges required, no user interaction, and partial confidentiality impact. No patches or public exploits are currently available, but the vulnerability's presence in a popular plugin used by many European organizations makes it a significant concern. The SSRF can be used to scan internal networks, access metadata services, or interact with internal APIs, increasing the risk of lateral movement or data leakage.
Potential Impact
For European organizations, this vulnerability poses a risk of internal network reconnaissance and potential data exposure from internal services that are normally protected by network segmentation or firewalls. Since the vulnerability requires only Subscriber-level authentication, attackers can exploit it in environments with weak user registration controls or compromised credentials. This can lead to unauthorized access to sensitive internal resources, including internal APIs, databases, or cloud metadata services, which may result in information disclosure or facilitate further attacks. The impact on confidentiality is moderate, while integrity and availability impacts are minimal. Organizations relying heavily on WordPress with Elementor and this plugin are at risk of targeted attacks aiming to pivot into internal networks. The vulnerability could also be leveraged in multi-tenant hosting environments to attack other tenants or infrastructure. Given the widespread use of WordPress and Elementor in Europe, especially in small and medium enterprises and public sector websites, the potential impact is significant if left unmitigated.
Mitigation Recommendations
1. Immediately update the Element Pack Addons for Elementor plugin to a patched version once available. 2. If no patch is available, restrict access to the wp_ajax_import_elementor_template AJAX action by implementing web application firewall (WAF) rules that block or monitor suspicious requests targeting this endpoint. 3. Limit user registration and enforce strong authentication controls to reduce the risk of attacker access with Subscriber-level privileges. 4. Employ network segmentation and internal service access controls to minimize the impact of SSRF by restricting what internal resources the web server can reach. 5. Monitor logs for unusual outbound HTTP requests originating from the web server, especially to internal IP ranges or unexpected external destinations. 6. Consider disabling or removing the plugin if it is not essential to reduce the attack surface. 7. Conduct internal security assessments to identify any potential exploitation attempts and verify the integrity of internal services. 8. Educate administrators and developers about SSRF risks and secure coding practices to prevent similar vulnerabilities.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-10-08T22:16:18.680Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68f6ac1bd243d1f5a41c5f18
Added to database: 10/20/2025, 9:39:39 PM
Last enriched: 10/20/2025, 9:41:58 PM
Last updated: 10/21/2025, 2:29:46 AM
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
Self-Propagating GlassWorm Attacks VS Code Supply Chain
MediumNew Microchip Tech Protects Vehicles from Laser Attacks
MediumFlawed Vendor Guidance Exposes Enterprises to Avoidable Risk
MediumIs Your Car a BYOD Risk? Researchers Demonstrate How
MediumInternational Sting Takes Down SIM Box Criminal Network
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.