Element Pack Addons CVE-2025-11536
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain Subscriber-level account
-
DeliverySend wp_ajax_import_elementor_template request with internal URL
-
ExploitServer performs attacker-directed outbound request
-
ExecutionProbe and interact with internal services
-
ImpactExfiltrate internal metadata or modify internal service state
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated account with Subscriber-level access or above (PR:L) and invocation of the plugin's wp_ajax_import_elementor_template AJAX endpoint; the site must run Element Pack Addons for Elementor version 8.2.5 or earlier. The practical risk is amplified when the WordPress site permits open user self-registration, since that grants any visitor the Subscriber role needed. Limiting factors: it is NOT exploitable by fully unauthenticated attackers, the SSRF is blind (no response body returned to the attacker, constraining data theft), and meaningful impact depends on the presence of reachable internal services (e.g., cloud metadata endpoints, internal APIs) from the web server's network position. |
| Impact | This is a genuine but moderate-priority issue, and the available signals are largely consistent rather than conflicting. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N, base 5.0) indicates a network-reachable, low-complexity attack that requires authentication at Subscriber level (PR:L) with no user interaction, and a scope change (S:C) because requests pivot from the web application into internal services. EPSS is low at 0.24% (14th percentile), the vulnerability is NOT listed in CISA KEV, and no public exploit code is indicated - so there is no public exploit identified at time of analysis and no evidence of active exploitation. The main risk driver is the low privilege barrier: WordPress sites frequently allow open/self-service Subscriber registration, which effectively lowers PR:L toward 'any registered user.' The impact ceiling is bounded - this is a blind SSRF (no direct response data returned), so confidentiality impact is limited and there is no direct integrity or availability impact to the host application. Net: a real, patch-worthy flaw useful for internal reconnaissance and reaching metadata/internal endpoints, but not a drop-everything emergency absent exploitation signals. The CVSS vector and the description agree on network vector and authenticated access, so no cross-source contradiction needs vendor verification here. |
| Exploit ScenarioDerived | An attacker registers (or compromises) a low-privilege Subscriber account on a WordPress site running Element Pack Addons for Elementor <= 8.2.5, then invokes the wp_ajax_import_elementor_template AJAX action with an attacker-controlled URL. The server issues an outbound request to that URL, allowing the attacker to probe internal-only services (e.g., cloud metadata endpoints or internal admin panels) from the trusted server context. No public exploit code is identified at time of analysis, and because the SSRF is blind, the attacker infers results from timing/behavioral side effects rather than direct response content. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Blind server-side request forgery in the Element Pack Addons for Elementor WordPress plugin (all versions up to and including 8.2.5) allows an authenticated user with Subscriber-level access or above to force the web server to issue HTTP requests to arbitrary internal destinations through the wp_ajax_import_elementor_template AJAX action. Because Subscriber is the lowest standard WordPress role, the exposure widens sharply on any site that permits open self-registration, where any visitor can obtain the necessary account. The request is blind (no response body is returned to the attacker), so impact is constrained to inference-based reconnaissance, internal port/service probing, and potential modification of internal services; CVSS 3.1 scores it 5.0 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N), reflecting the cross-boundary scope change but limited confidentiality-only effect. EPSS is low at 0.24% (14th percentile), the issue is not listed in CISA KEV, and no public exploit code was identified at time of analysis, making this a moderate-priority, patch-when-convenient finding rather than an emergency.
RemediationAI
No vendor-released patch version is specified in the provided intelligence, but because the advisory states that all versions up to and including 8.2.5 are vulnerable, the primary remediation is to update Element Pack Addons for Elementor to a release later than 8.2.5 and confirm the exact fixed version in the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/97c100c3-8a96-4198-b38a-206268ff20ec?source=cve; if no patched release is yet installed, disabling the plugin is the only fully effective control. Where the plugin must remain active, close the easiest exploitation path by disabling open user self-registration in WordPress (Settings > General) and auditing existing Subscriber accounts, since any self-registered user meets the PR:L prerequisite - the trade-off is loss of self-service signup and potential impact on membership or comment workflows. Restrict who can trigger the elementor template import/setup-wizard functionality (for example by tightening the capability check or blocking the wp_ajax_import_elementor_template action with a WAF rule for low-privilege roles); this may interfere with legitimate administrators using the setup wizard. As defence in depth, apply outbound egress filtering on the web server so it can only reach allowlisted external destinations (this can break legitimate plugin update, license, or API calls and requires tuning), and enforce cloud IMDSv2 or disable instance metadata access from the WordPress host to blunt credential-theft paths if the SSRF is chained. Given the blind nature of the request and the low EPSS (0.24%), these mitigations can be prioritised after any higher-risk findings, but should not be deferred indefinitely.
Affected ProductsAI
Element Pack Addons for Elementor (WordPress plugin, distributed as Element Pack Lite / bdthemes-element-pack-lite) is affected in all versions up to and including 8.2.5; the vendor source reference in the advisory points to the 8.2.4 tag, confirming the vulnerable branch in the 8.x line. The plugin runs as a standard WordPress extension and requires an active Elementor installation; the vulnerable surface is available whenever the plugin is enabled and WordPress permits authenticated AJAX calls from Subscriber-level users. No CPE identifiers were supplied in the intelligence feed, so version matching should be done against the plugin slug (bdthemes-element-pack-lite) and installed version number. The authoritative affected-version statement and the corresponding fixed release are documented in the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/97c100c3-8a96-4198-b38a-206268ff20ec?source=cve.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-918 (Server-Side Request Forgery): a user-supplied URL passed into the plugin's Elementor template import routine is fetched by the server without validating that the destination host is external and safe. The vulnerable code path sits in the plugin's setup-wizard logic (see includes/setup-wizard/init.php around line 420 in the 8.2.4 tag) and is reachable through the WordPress AJAX pattern wp_ajax_import_elementor_template, which registers a handler for authenticated users. The fetch is blind, meaning the HTTP response from the targeted internal endpoint is not relayed back to the caller, so an attacker cannot simply read internal content; instead they must rely on timing differences, error behaviour, and side effects of the request. That still permits meaningful abuse: probing internal hosts and ports, reaching internal-only REST APIs, and hitting cloud instance metadata endpoints (for example 169.254.169.254) if the web server runs in a cloud network without IMDS hardening. CWE-918 is the canonical SSRF class, and the CVSS scope-change flag (S:C) is appropriate here because a successful exploit lets the application act as a proxy into network segments that are not supposed to be reachable from the public-facing WordPress install.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
Network-reachable AJAX action (AV:N/AC:L) needs a Subscriber account (PR:L); SSRF pivots into other systems (S:C); blind nature yields only limited confidentiality (C:L), no direct integrity/availability loss.
Primary rating from Vendor (wordfence).
CVSS VectorVendor: wordfence
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB