CVE-2025-11536
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Element Pack Addons for Elementor WordPress plugin versions up to 8.2.5 contains a blind Server-Side Request Forgery (SSRF) vulnerability in the wp_ajax_import_elementor_template AJAX action. Authenticated attackers with Subscriber-level access or higher can abuse this to make the server perform requests to arbitrary URLs, potentially accessing internal services and exfiltrating data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Element Pack Addons plugin is installedCheck your WordPress plugins directory or use WP-CLI: wp plugin list --status=active --field=name | grep 'element-pack'Affected if The plugin is installed and active in your WordPress environment
-
Check the installed version numberUse WP-CLI: wp plugin get bdthemes-element-pack --field=version, or check the plugin header in wp-content/plugins/bdthemes-element-pack/bdthemes-element-pack.phpAffected if The version is 8.2.5 or lower (any version up to and including 8.2.5 is affected)
-
Confirm the vulnerable AJAX endpoint existsSearch the plugin files for 'wp_ajax_import_elementor_template' action hook registration, typically in the main plugin file or an includes/AJAX.php fileAffected if The wp_ajax_import_elementor_template hook is registered in the plugin code
-
Verify the endpoint accessibilityTest if the AJAX action responds without proper capability checks by inspecting the code handling import_elementor_template, looking for current_user_can() or a capability gateAffected if The AJAX handler lacks proper capability validation or allows subscriber-level access (contributor or above)
-
Check for existing authentication requirementsReview the AJAX callback function for nonce verification (check_ajax_referer or wp_verify_nonce) and access control (current_user_can with a role like edit_posts)Affected if No nonce check or weak capability check (like 'read' instead of 'manage_options') is present
If the plugin is active, the version is 8.2.5 or lower, and the import_elementor_template AJAX endpoint is accessible to subscriber-level users without proper nonce or capability validation, your environment is affected by this SSRF vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Element Pack Addons plugin to a patched version beyond 8.2.5. Until patched, consider disabling the plugin or using a WAF to block the vulnerable AJAX endpoint.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11536 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11536 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data