dbcve.org
Magical Addons For ElementorWordPress extension · Wpthemespace

CVE-2024-38730

MEDIUM · 6.4 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 1.1.42 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Server-Side Request Forgery (SSRF) vulnerability in Noor alam Magical Addons For Elementor.This issue affects Magical Addons For Elementor: from n/a through 1.1.41.

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 · moderate confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in the Magical Addons For Elementor WordPress plugin (versions through 1.1.41). The vulnerability likely allows an attacker to induce the server to make arbitrary HTTP requests to internal or external resources, potentially accessing internal services, cloud metadata endpoints, or bypassing network restrictions.

MitigationUpdate to the latest version of Magical Addons For Elementor when a patch is released. Until then, restrict access to the plugin's admin interface and consider disabling the affected functionality if possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Magical Addons For ElementorWordPress extension
Affected:< 1.1.42

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Magical Addons For Elementor' by Wpthemespace, or check the wp-content/plugins/ directory for a folder containing 'magical' or 'wpthemespace' in the name.
    Affected if The plugin is present in the plugins directory or listed in WordPress admin.
  2. Identify the installed version
    In WordPress admin > Plugins > Magical Addons For Elementor, click on the plugin name to view details and note the version number. Alternatively, open the main plugin PHP file (usually in wp-content/plugins/[plugin-folder]/[plugin-folder].php) and look for a version constant or header comment.
    Affected if The version number displayed is lower than 1.1.42 (for example, 1.1.41, 1.1.40, etc.).
  3. Verify the plugin is active
    In WordPress admin > Plugins, check if 'Magical Addons For Elementor' shows as 'Active' rather than 'Inactive' or 'Not Activated'.
    Affected if The plugin is currently activated on the WordPress site.
  4. Check for the vulnerable HTTP request functionality
    Review the plugin settings in WordPress admin (typically under Elementor > Settings or a dedicated 'Magical Addons' menu) for any features that make external HTTP requests, such as remote template import, API connections, or webhook integrations.
    Affected if Any feature that sends HTTP requests is enabled or configured on the site.

You are affected if Magical Addons For Elementor is installed, active, and running version 1.1.41 or lower.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.1.42 or later
Fixed in 1.1.42
Interim mitigation

Update to the latest version of Magical Addons For Elementor when a patch is released. Until then, restrict access to the plugin's admin interface and consider disabling the affected functionality if possible.

Recommended fix High confidence

1.1.42

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Find 'Magical Addons For Elementor' in the plugin list.
  4. 4. Click 'Update Now' if an update is available, or manually download version 1.1.42 from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin.
  5. 5. After updating, verify the plugin version shows 1.1.42 in the Plugins list.
  6. 6. Test that Elementor page builder functionality still works correctly with the updated plugin.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Magical Addons For Elementor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38730 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-38730 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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