dbcve.org
Move Addons For ElementorWordPress extension · Moveaddons

CVE-2024-34562

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-08
Fix available
A fix is available. Upgrade to 1.3.1 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 allows Stored XSS.This issue affects Move Addons for Elementor: from n/a through 1.3.0.

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.0. The vulnerability allows authenticated or unauthenticated attackers to inject malicious JavaScript code into plugin settings or content areas that are rendered without proper input sanitization or output escaping, causing the script to execute in the browsers of users viewing the affected pages.

MitigationUsers should immediately remove or replace Move Addons for Elementor as the plugin appears unmaintained with no official patch available. If continued use is required, implement aggressive output escaping at theme/template level or deploy a Web Application Firewall to filter malicious payloads.

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

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 Move Addons For Elementor is installed
    Check the WordPress plugins directory for the moveaddons folder, typically located at /wp-content/plugins/move-addons-for-elementor/ or similar path containing 'moveaddons'
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed version
    Open the plugin's main file or readme.txt and locate the version number declared in the plugin header
    Affected if The version is 1.3.0 or below (any version less than 1.3.1)
  3. Confirm the plugin is active
    Check the WordPress database wp_options table for option_name 'active_plugins' or use the WordPress admin plugins list to verify the plugin status
    Affected if The plugin appears in the list of active plugins
  4. Check for accessible plugin settings pages
    Access the WordPress admin dashboard and navigate to the Move Addons settings pages (typically under Elementor > Move Addons or a dedicated admin menu item)
    Affected if Settings pages are accessible without restriction
  5. Inspect for existing malicious script injections
    Examine the wp_options table or relevant plugin custom post types/options for any suspicious script tags, encoded payloads, or unexpected HTML/JS content in fields that could be rendered on the frontend
    Affected if Unexpected script tags or encoded JavaScript are found in plugin settings or content storage

You are affected if Move Addons For Elementor is installed, active, and running version 1.3.0 or lower, as this version lacks proper input sanitization and output escaping in its settings or content rendering.

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.1 or later
Fixed in 1.3.1
Interim mitigation

Users should immediately remove or replace Move Addons for Elementor as the plugin appears unmaintained with no official patch available. If continued use is required, implement aggressive output escaping at theme/template level or deploy a Web Application Firewall to filter malicious payloads.

Recommended fix Moderate confidence

1.3.1

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin > Plugins > Move Addons for Elementor
  3. Update Move Addons for Elementor to version 1.3.1
  4. After updating, clear any caching plugins or server-side caches
  5. Test the updated plugin functionality to ensure normal operation
  6. Verify the XSS vulnerability is no longer present by testing input fields that were previously vulnerable

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

Fix this in Move Addons For Elementor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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