dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2024-56062

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-31
Fix available
A fix is available. Upgrade to after 1.3.987 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 WP Royal Royal Elementor Addons royal-elementor-addons allows Stored XSS.This issue affects Royal Elementor Addons: from n/a through <= 1.3.987.

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 the Royal Elementor Addons WordPress plugin. The vulnerability allows an attacker to inject malicious JavaScript code through improper input validation, which is then stored in the database and executed when other users view affected pages within the plugin's components.

MitigationUpgrade Royal Elementor Addons to the latest version available from the vendor to obtain the patched code. Alternatively, if no update is available, review and sanitize all user-supplied input in the plugin's code paths, particularly in form fields and content rendering areas.

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
Royal Elementor AddonsWordPress extension
Affected:<= 1.3.987

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. Locate the Royal Elementor Addons plugin
    Navigate to wp-content/plugins/ in your WordPress installation and confirm the presence of a folder named 'royal-elementor-addons' or check the Plugins page in WordPress admin
    Affected if The plugin folder exists in the WordPress installation
  2. Identify the installed version number
    Open the main plugin file (usually royal-elementor-addons.php) and locate the 'Version:' header in the file header comments, or view the version listed on the WordPress admin Plugins page
    Affected if Version is displayed as 1.3.987 or lower
  3. Compare against affected version range
    Compare your identified version to the affected range: any version less than or equal to 1.3.987 is within the affected range
    Affected if Your installed version is 1.3.987 or any earlier version number
  4. Determine if plugin features are active
    Review whether the plugin's components, particularly any form builders or content rendering elements, are actively used on your site (check pages built with Elementor that include Royal Elementor widgets)
    Affected if The plugin is active and its interactive components or forms are in use on published pages

You are affected if Royal Elementor Addons is installed with version 1.3.987 or lower and its interactive components are actively displayed on your site.

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.3.987
Interim mitigation

Upgrade Royal Elementor Addons to the latest version available from the vendor to obtain the patched code. Alternatively, if no update is available, review and sanitize all user-supplied input in the plugin's code paths, particularly in form fields and content rendering areas.

Recommended fix Moderate confidence

Royal Elementor Addons version > 1.3.987 (latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Royal Elementor Addons in the plugin list
  4. Check if the current version is 1.3.987 or lower
  5. If vulnerable, click 'Update Now' to install the latest version, or manually download the update from wordpress.org
  6. After updating, verify the plugin version shows a version greater than 1.3.987
  7. Clear any caching plugins if present
  8. Test that the WordPress site functions normally after the update

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

Fix this in Royal Elementor Addons 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-56062 — 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-56062 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