Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11536: CWE-918 Server-Side Request Forgery (SSRF) in bdthemes Element Pack Addons for Elementor

0
Medium
VulnerabilityCVE-2025-11536cvecve-2025-11536cwe-918
Published: Mon Oct 20 2025 (10/20/2025, 21:23:48 UTC)
Source: CVE Database V5
Vendor/Project: bdthemes
Product: 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

Machine-generated threat intelligence

AILast updated: 02/27/2026, 19:07:42 UTC

Technical Analysis

CVE-2025-11536 is a server-side request forgery (SSRF) vulnerability classified under CWE-918, found in the Element Pack Addons for Elementor WordPress plugin developed by bdthemes. This vulnerability exists in all versions up to and including 8.2.5 and is triggered via the wp_ajax_import_elementor_template AJAX action. An attacker with at least Subscriber-level privileges can exploit this flaw to make the server perform HTTP requests to arbitrary URLs, including internal network resources that are not normally accessible externally. The SSRF is 'blind,' meaning the attacker may not directly see the response but can infer information based on side effects or timing. This can be leveraged to query internal services, potentially leading to information disclosure or further attacks such as internal network scanning or accessing metadata services. The vulnerability requires authentication but no additional user interaction. The CVSS v3.1 base score is 5.0, reflecting medium severity due to the limited scope of impact (confidentiality impact only) and the requirement for authenticated access. No patches or known exploits are currently available, but the vulnerability poses a risk to WordPress sites using this plugin, especially those with sensitive internal services behind firewalls.

Potential Impact

The primary impact of this SSRF vulnerability is unauthorized information disclosure from internal network services that are normally inaccessible from the internet. Attackers with low-level authenticated access (Subscriber or higher) can leverage the vulnerability to perform reconnaissance on internal infrastructure, potentially discovering sensitive endpoints such as internal APIs, databases, or cloud metadata services. This can facilitate further attacks like privilege escalation, lateral movement, or data exfiltration. Although the vulnerability does not directly allow modification or denial of service, the information gained can significantly weaken an organization's security posture. Organizations running WordPress sites with this plugin are at risk, especially if internal services are exposed on the same network. The medium CVSS score reflects moderate risk, but the impact could be higher in environments with critical internal services accessible via SSRF. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits once the vulnerability is public.

Mitigation Recommendations

To mitigate CVE-2025-11536, organizations should first update the Element Pack Addons for Elementor plugin to a patched version once it becomes available. Until a patch is released, administrators should restrict plugin usage to trusted users only and consider disabling or restricting the wp_ajax_import_elementor_template AJAX action if possible. Implementing web application firewall (WAF) rules to detect and block suspicious SSRF patterns targeting this AJAX endpoint can reduce exploitation risk. Network segmentation should be enforced to limit the WordPress server's ability to access sensitive internal services. Additionally, internal services should require strong authentication and not rely solely on network isolation. Monitoring logs for unusual outbound requests originating from the WordPress server can help detect exploitation attempts. Finally, review user roles and permissions to minimize the number of users with Subscriber or higher privileges who can access the vulnerable functionality.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

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: 2/27/2026, 7:07:42 PM

Last updated: 3/24/2026, 2:10:23 AM

Views: 243

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses