dbcve.org
Magical Addons For ElementorWordPress extension · Wpthemespace

CVE-2024-54212

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-06
Fix available
A fix is available. Upgrade to after 1.2.6 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 magical-addons-for-elementor allows Stored XSS.This issue affects Magical Addons For Elementor: from n/a through <= 1.3.6.

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 XSS vulnerability in Magical Addons For Elementor plugin allows attackers to inject malicious scripts that persist on the server and execute when other users (typically administrators) view the affected content. The CVSS 5.4 indicates moderate impact with user interaction required.

MitigationUpdate to a patched version of the plugin when available. Until then, restrict access to the affected plugin features and sanitize all user inputs with WordPress escaping functions (esc_html, esc_attr, wp_kses) before output.

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

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. Verify Magical Addons For Elementor is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Magical Addons For Elementor' by Wpthemespace
    Affected if Plugin is not found in the installed plugins list
  2. Check installed version number
    View the plugin details page or check the plugin header in /wp-content/plugins/magical-addons-for-elementor/ directory for the Version field
    Affected if Version is 1.2.6 or lower (any version <= 1.2.6)
  3. Identify plugin widgets or features in use
    Review pages/posts created with Elementor and check the Elementor widget panel for any Magical Addons widgets currently inserted
    Affected if Any Magical Addons widgets are actively used on the site
  4. Inspect stored content for suspicious scripts
    Search WordPress postmeta and options tables for any encoded or obfuscated JavaScript patterns (script tags, javascript: URIs, event handlers) within Magical Addons-related meta keys
    Affected if Unexpected script tags or JavaScript code is found in plugin-related content

If the plugin is installed with version 1.2.6 or lower and Magical Addons widgets are in use, the environment is potentially affected by this stored XSS vulnerability.

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 a release after 1.2.6
Interim mitigation

Update to a patched version of the plugin when available. Until then, restrict access to the affected plugin features and sanitize all user inputs with WordPress escaping functions (esc_html, esc_attr, wp_kses) before output.

Recommended fix Moderate confidence

Version 1.3.7 or later (latest available version)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Magical Addons For Elementor' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running on version 1.3.7 or higher
  6. 6. Test that the Elementor widgets using Magical Addons are functioning correctly on the frontend

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

Fix this in Magical Addons For Elementor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,310
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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