dbcve.org
Magical Addons For ElementorWordPress extension · Wpthemespace

CVE-2024-34547

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-08
Fix available
A fix is available. Upgrade to 1.1.35 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Noor alam Magical Addons For Elementor allows Stored XSS.This issue affects Magical Addons For Elementor: from n/a through 1.1.34.

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

Stored Cross-site Scripting (XSS) vulnerability in Magical Addons For Elementor plugin allows attackers to inject malicious JavaScript through unsanitized input fields. The injected script executes in the browsers of users who view affected pages, potentially leading to session hijacking, credential theft, or defacement.

MitigationUpgrade to a version newer than 1.1.34, or apply input validation and output encoding to all user-supplied data before rendering in HTML contexts.

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.35

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 Magical Addons For Elementor is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Magical Addons For Elementor' by Wpthemespace in the list
    Affected if The plugin appears in the installed plugins list
  2. Check installed version number
    In Plugins list, click 'View Details' on Magical Addons For Elementor, or check the plugin header in wp-content/plugins/magical-addons-for-elementor/readme.txt for the Version field
    Affected if The version number displayed is below 1.1.35 (e.g., 1.1.34, 1.1.33, etc.)
  3. Identify which Magical Addons widgets are in use
    Edit a page/post with Elementor, open the widget panel, and look for widgets under the 'Magical Addons' category. Common vulnerable widgets include forms, input fields, and display widgets that accept user-supplied text
    Affected if Any Magical Addons widgets are inserted and published on live pages
  4. Inspect database for suspicious script tags
    Use phpMyAdmin or WP-CLI to search the wp_postmeta and wp_posts tables for meta values or content containing '<script' tags, 'javascript:', or 'onerror=' related to recent posts using Elementor
    Affected if Any records contain script tags or event handlers (onclick, onerror, onload) that were not intentionally added by an administrator
  5. Review recent Elementor editor activity
    Check WordPress revision history or activity logs for any changes made to pages containing Magical Addons widgets that include unexpected HTML, JavaScript, or encoded content
    Affected if Revisions show sudden addition of script tags or unusual encoded content in fields controlled by Magical Addons widgets

You are affected if Magical Addons For Elementor is installed and the installed version is below 1.1.35, and any pages use the plugin's widgets with user-accessible input fields.

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.35 or later
Fixed in 1.1.35
Interim mitigation

Upgrade to a version newer than 1.1.34, or apply input validation and output encoding to all user-supplied data before rendering in HTML contexts.

Recommended fix Moderate confidence

1.1.35

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Magical Addons For Elementor' in the plugin list
  4. Check if current version is below 1.1.35
  5. If below 1.1.35, click 'Update now' to upgrade to version 1.1.35 or later
  6. Verify the update was successful and the new version is 1.1.35 or higher

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

Fix this in Magical Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34547 — 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-34547 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