dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2024-9059

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 Google Maps widget in all versions up to, and including, 1.7.1001 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 contains a stored XSS vulnerability in its Google Maps widget. Versions up to 1.7.1001 fail to properly sanitize user inputs and escape outputs, allowing authenticated attackers with Contributor-level permissions to inject malicious JavaScript that executes whenever users access affected pages.

MitigationUpdate the Royal Elementor Addons plugin to version 1.7.1002 or later. Additionally, audit existing pages using the Google Maps widget for injected malicious scripts and consider restricting widget permissions until the patch is applied.

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. Verify Royal Elementor Addons plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Royal Elementor Addons' in the list. Note the installed version number displayed next to the plugin name.
    Affected if The plugin is installed and the version shown is below 1.7.1002 (e.g., 1.7.1001, 1.7.1000, etc.)
  2. Check if the Google Maps widget is in use
    Navigate to Pages or Posts in the WordPress admin. Edit any pages that may contain the Royal Elementor Addons Google Maps widget. Open the page with Elementor editor and search for the Google Maps widget in the widget list or on the page canvas.
    Affected if The Google Maps widget from Royal Elementor Addons is present on any published or draft page/post
  3. Inspect the Google Maps widget settings for suspicious content
    With the page in Elementor editor, click on the Google Maps widget to open its settings panel. Examine all input fields (especially address, map title, or custom coordinates) for any unexpected script tags, event handlers (onclick, onload, onerror), or suspicious-looking URLs.
    Affected if Any Google Maps widget contains unexpected HTML/script content in its configuration fields that was not intentionally added by an administrator
  4. Review user accounts with Contributor-level access
    Go to Users > All Users in WordPress admin. Identify any accounts with the 'Contributor' role. These users have permission to create and edit posts, which would give them access to inject XSS via the vulnerable widget.
    Affected if There are one or more Contributor-level user accounts on the site, and the plugin version is below 1.7.1002, and Google Maps widgets exist on the site

You are affected if Royal Elementor Addons version is below 1.7.1002 AND the Google Maps widget is in use on any page, especially when Contributor-level users have access to edit content.

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 the Royal Elementor Addons plugin to version 1.7.1002 or later. Additionally, audit existing pages using the Google Maps widget for injected malicious scripts and consider restricting widget permissions until the patch is applied.

Recommended fix High confidence

1.7.1002

  1. Update the Royal Elementor Addons and Templates plugin to version 1.7.1002 or later through the WordPress admin dashboard (Plugins > All Plugins > Royal Elementor Addons > Update Now)

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.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-9059 — 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-9059 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