dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2024-3887

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-16
Fix available
A fix is available. Upgrade to 1.3.975 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 Form Builder widget in all versions up to, and including, 1.3.974 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 and Templates WordPress plugin versions up to 1.3.974 contain a stored XSS vulnerability in the Form Builder widget. Authenticated contributors and above can inject arbitrary JavaScript through insufficiently sanitized user-supplied attributes, which executes when other users access the compromised pages.

MitigationUpdate the Royal Elementor Addons and Templates plugin to version 1.3.975 or later, which includes proper input sanitization and output escaping for the Form Builder widget attributes.

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

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. Confirm Royal Elementor Addons plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Royal Elementor Addons and Templates'. Note the installed version number displayed next to the plugin name.
    Affected if The plugin is installed and the version shown is lower than 1.3.975 (for example, 1.3.974, 1.3.96, etc.)
  2. Verify Form Builder widget usage on the site
    Check your WordPress pages, posts, or Elementor templates for any instance where the Form Builder widget has been added to a layout. In Elementor editor, search for 'Form Builder' in the widget panel.
    Affected if The Form Builder widget is present on any published page, post, or template on the site.
  3. Inspect Form Builder widget configuration in the database
    Query the WordPress database postmeta table for Form Builder widget data. Look for meta_key values containing 'elementor_data' where the meta_value includes 'form-builder' or the widget name. Use: SELECT * FROM wp_postmeta WHERE meta_value LIKE '%form-builder%' (adjust prefix if different).
    Affected if Any Form Builder widget configurations are found in the database containing unsanitized HTML or JavaScript in attributes like label, name, or placeholder fields.
  4. Review Elementor page data for suspicious stored scripts
    Examine the raw meta_value from wp_postmeta for posts/pages using the Form Builder. Look for script tags, javascript: URIs, or event handlers (onclick, onerror, onload) within Form Builder field configurations.
    Affected if The Form Builder widget data contains raw HTML tags, script elements, or event handler attributes that were not escaped during save.

A user is affected if the Royal Elementor Addons plugin version is below 1.3.975 AND the Form Builder widget has been used on the site, as the stored XSS can execute when other users view pages containing that widget.

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.975 or later
Fixed in 1.3.975
Interim mitigation

Update the Royal Elementor Addons and Templates plugin to version 1.3.975 or later, which includes proper input sanitization and output escaping for the Form Builder widget attributes.

Recommended fix High confidence

1.3.975

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find 'Royal Elementor Addons' in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 1.3.975
  5. After updating, verify the plugin version shows 1.3.975 or higher

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
  • Testing3.0 h
  • Review / QA2.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-3887 — 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-3887 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