dbcve.org
Move Addons For ElementorWordPress extension · Moveaddons

CVE-2024-47364

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-06
Fix available
A fix is available. Upgrade to 1.3.5 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 moveaddons Move Addons for Elementor move-addons allows Stored XSS.This issue affects Move Addons for Elementor: from n/a through <= 1.3.4.

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

A stored Cross-Site Scripting (XSS) vulnerability exists in Move Addons for Elementor plugin versions through 1.3.4. The vulnerability stems from improper neutralization of user-supplied input during web page generation, allowing attackers to inject malicious JavaScript that persists and executes when other users view affected pages rendered by the plugin.

MitigationUpdate to a patched version of Move Addons for Elementor if available. Otherwise, implement proper input sanitization and output encoding for all user-supplied data before rendering in web pages.

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
Move Addons For ElementorWordPress extension
Affected:< 1.3.5

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. Check installed plugin version
    Navigate to WordPress dashboard > Plugins > Move Addons For Elementor and verify the version number displayed. Alternatively, inspect the plugin's main PHP file (typically moveaddons.php in wp-content/plugins/move-addons) for the 'Version' header in the plugin comment block.
    Affected if The displayed version number is 1.3.4 or lower (any version below 1.3.5).
  2. Confirm plugin is active
    Verify the Move Addons For Elementor plugin status shows as 'Active' in the WordPress Plugins admin page.
    Affected if The plugin is active and running on the WordPress site.
  3. Identify plugin widgets in use
    Check Elementor pages, posts, or templates by editing them with Elementor and searching the widget panel for 'Move Addons' widgets. Inspect any pages using these widgets in the WordPress pages/posts list.
    Affected if Any Elementor page or template is using Move Addons widgets that accept and display user-supplied input.
  4. Inspect stored data for unsanitized input
    Review the WordPress database (wp_postmeta table) or the plugin's own database tables for any custom fields, widget settings, or content stored by the plugin that may contain HTML or JavaScript code.
    Affected if Stored data contains unescaped HTML tags or script elements that could execute in a user's browser.

If the plugin version is 1.3.4 or lower and the plugin is active with any of its widgets in use on pages, the environment is 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 1.3.5 or later
Fixed in 1.3.5
Interim mitigation

Update to a patched version of Move Addons for Elementor if available. Otherwise, implement proper input sanitization and output encoding for all user-supplied data before rendering in web pages.

Recommended fix High confidence

1.3.5

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Locate 'Move Addons for Elementor' in the plugin list
  5. 5. If an update is available, click 'Update Now' to update to version 1.3.5 or later
  6. 6. If no automatic update is available, download version 1.3.5 from the official WordPress repository or the plugin vendor
  7. 7. Deactivate the existing Move Addons for Elementor plugin
  8. 8. Delete the existing plugin files

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

Fix this in Move Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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