dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2024-8482

MEDIUM · 6.4 CVSS v3.1 Published 2024-10-08
Fix available
A fix is available. Upgrade to 1.3.987 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Royal Elementor Addons and Templates plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘url’ parameter in all versions up to, and including, 1.3.982 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 · high confidence

The Royal Elementor Addons plugin for WordPress is vulnerable to stored XSS via the 'url' parameter due to insufficient input sanitization and output escaping. Authenticated attackers with Contributor-level access can inject arbitrary JavaScript that executes whenever users access the affected pages.

MitigationUpdate Royal Elementor Addons to version 1.3.983 or later which includes proper sanitization and escaping for the url parameter.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 plugin installation
    Navigate to WordPress admin > Plugins and look for 'Royal Elementor Addons' in the installed plugins list, or inspect the /wp-content/plugins/ directory for a folder named 'royal-elementor-addons'
    Affected if The plugin is not installed or not present on the system
  2. Check installed version
    In WordPress admin > Plugins, click on the plugin to view version details, or read the 'Version' field in the plugin header from the main plugin file (typically /wp-content/plugins/royal-elementor-addons/wrapper.php or similar main file)
    Affected if The displayed version number is lower than 1.3.987 (e.g., 1.3.986, 1.3.980, etc.)
  3. Identify user roles with access
    Navigate to WordPress admin > Users and review which user roles exist. The vulnerability is exploitable by users with Contributor-level access or higher.
    Affected if Any user role with Contributor-level or higher permissions exists on the site (this is the typical default in WordPress)
  4. Locate the url parameter feature
    The vulnerability exists in a feature that accepts a 'url' parameter. Review Royal Elementor Addons widget settings, particularly any widget that accepts URL input (such as button, link, or navigation widgets).
    Affected if Any widget or element within the plugin that accepts user-supplied URL input is in use on pages/posts

The site is affected if Royal Elementor Addons is installed with a version lower than 1.3.987 and the plugin or any of its URL-accepting widgets are actively in use.

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.987 or later
Fixed in 1.3.987
Interim mitigation

Update Royal Elementor Addons to version 1.3.983 or later which includes proper sanitization and escaping for the url parameter.

Recommended fix High confidence

1.3.987 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Royal Elementor Addons and Templates' in the plugin list
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, navigate to Dashboard > Updates to check and apply updates
  6. After updating, verify the plugin version is 1.3.987 or higher by checking the Plugins page

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

Fix this in Royal Elementor Addons Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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