dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2024-9682

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-13
Fix available
A fix is available. Upgrade to 1.7.1002 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
The Royal Elementor Addons and Templates plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Form Builder widget in all versions up to, and including, 1.7.1001 due to insufficient input sanitization and output escaping on user supplied attributes. 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 before version 1.7.1002 contains a stored XSS vulnerability in its Form Builder widget. Authenticated users with contributor-level access can inject malicious JavaScript through unsanitized widget attributes. The injected scripts execute in the browsers of any user viewing the affected pages.

MitigationUpdate Royal Elementor Addons and Templates to version 1.7.1002 or later. Until then, restrict Form Builder widget access to only trusted users and audit existing pages using this widget.

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

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 if Royal Elementor Addons plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Royal Elementor Addons and Templates'. Note the installed version displayed there.
    Affected if The plugin is listed with a version number lower than 1.7.1002, or the version cannot be determined (plugin may be outdated).
  2. Verify the exact plugin version
    Open the plugin file 'royal-elementor-addons.php' in the plugin directory and locate the 'Version' defined constant or header comment.
    Affected if The version string shows a number less than 1.7.1002 (for example, 1.7.1001, 1.7.100, 1.7.9, etc.).
  3. Identify pages using the Form Builder widget
    In WordPress admin with Elementor active, go to Pages or Posts and search for any that were edited with Elementor. Open each in Elementor editor and look in the widget panel for 'Form Builder' or 'Royal Form' widget under the Royal Addons category.
    Affected if Any published page or post contains the Form Builder widget from Royal Elementor Addons.
  4. Review user roles with Form Builder access
    Go to WordPress Users > All Users and identify accounts with Contributor, Author, Editor, or Administrator roles who have access to create or edit content using Elementor.
    Affected if There are user accounts with Contributor-level access or higher who can edit pages/posts containing the Form Builder widget.

If Royal Elementor Addons version is below 1.7.1002 AND the Form Builder widget is present on any live page, the site 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.7.1002 or later
Fixed in 1.7.1002
Interim mitigation

Update Royal Elementor Addons and Templates to version 1.7.1002 or later. Until then, restrict Form Builder widget access to only trusted users and audit existing pages using this widget.

Recommended fix High confidence

Royal Elementor Addons version 1.7.1002

  1. Navigate to WordPress dashboard > Plugins > Installed Plugins
  2. Locate Royal Elementor Addons and Templates plugin
  3. Check if current version is below 1.7.1002
  4. If vulnerable, click Update Now to upgrade to version 1.7.1002 or latest available version
  5. Verify the update completed successfully by confirming the new version number

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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