dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2024-31236

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-07
Fix available
A fix is available. Upgrade to 1.3.94 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 allows Stored XSS.This issue affects Royal Elementor Addons: from n/a through 1.3.93.

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

Stored XSS vulnerability in Royal Elementor Addons allows attackers to inject malicious JavaScript through unsanitized input that gets stored in the database and executed when other users view affected pages.

MitigationUpdate Royal Elementor Addons to version 1.3.94 or later once the patched version is released, after validating the fix addresses the XSS vector.

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

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 is installed
    Check WordPress plugin directory for 'royal-elementor-addons' folder, or run: wp plugin list --name='royal-elementor-addons'
    Affected if Plugin is not found in the installation
  2. Identify installed plugin version
    Check the plugin header in wp-content/plugins/royal-elementor-addons/plugin.php for 'Version:' field, or run: wp plugin get royal-elementor-addons --field=version
    Affected if Version is present but less than 1.3.94
  3. Inspect database for injected scripts
    Query the wp_postmeta table for entries containing script tags, iframe tags, or javascript: URIs in meta_value fields that may have been stored via plugin features (such as: SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script%' OR meta_value LIKE '%javascript:%')
    Affected if Any rows contain malicious script or iframe tags in meta values associated with plugin-generated content
  4. Review plugin-generated content for XSS payloads
    Search post content, custom post types created by the plugin, or widget/header/footer templates for suspicious onload, onerror, or event handler attributes
    Affected if Any plugin-managed content contains unsanitized JavaScript event handlers or suspicious URLs

User is affected if Royal Elementor Addons version is below 1.3.94, or if suspicious script injections are found in the database in content created by the plugin

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.94 or later
Fixed in 1.3.94
Interim mitigation

Update Royal Elementor Addons to version 1.3.94 or later once the patched version is released, after validating the fix addresses the XSS vector.

Recommended fix High confidence

Royal Elementor Addons version 1.3.94

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Royal Elementor Addons' in the plugin list
  4. Check if the current version is below 1.3.94
  5. If update available, click 'Update Now' to upgrade to version 1.3.94 or higher
  6. Alternatively, upload the latest version of Royal Elementor Addons from wordpress.org or your purchase source
  7. After update, verify the plugin version shows 1.3.94 or newer

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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