dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2024-50442

HIGH · 7.2 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 1.3.981 or later.
See remediation →
78/100
Remediation priority · High
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
Improper Restriction of XML External Entity Reference vulnerability in WP Royal Royal Elementor Addons royal-elementor-addons allows XML Injection.This issue affects Royal Elementor Addons: from n/a through <= 1.3.980.

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

This is an Improper Restriction of XML External Entity Reference (XXE) vulnerability in the WordPress Royal Elementor Addons plugin. The plugin improperly processes XML input, allowing attackers to inject malicious XML that can reference external entities, potentially leading to disclosure of internal files, SSRF, or denial of service.

MitigationUpdate to a patched version of Royal Elementor Addons when available. Until then, disable or restrict the plugin's XML parsing functionality and consider deploying a WAF rule to detect and block XXE attack patterns.

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

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 installed plugin version
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Locate 'Royal Elementor Addons' and note the version number displayed. Alternatively, inspect the plugin file header in wp-content/plugins/royal-elementor-addons/ for the 'Version' comment.
    Affected if Installed version is lower than 1.3.981
  2. Identify active XML processing features
    Review the Royal Elementor Addons settings pages in the WordPress admin under Elementor > Royal Elementor Addons or similar. Look for any features that accept or parse XML data, such as import templates, XML parsers, or data integration options.
    Affected if Any XML processing or import functionality is enabled and accessible
  3. Check for public-facing XML endpoints
    Inspect the plugin directory (wp-content/plugins/royal-elementor-addons/) for PHP files that handle XML input. Common file names may include parser, import, xml, or similar. Test accessible URLs that might process XML, particularly any import or template features.
    Affected if The plugin exposes any endpoint that processes XML input without proper validation

A user is affected if Royal Elementor Addons version is below 1.3.981 AND the plugin's XML parsing functionality is active and accessible on the site.

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.981 or later
Fixed in 1.3.981
Interim mitigation

Update to a patched version of Royal Elementor Addons when available. Until then, disable or restrict the plugin's XML parsing functionality and consider deploying a WAF rule to detect and block XXE attack patterns.

Recommended fix Moderate confidence

1.3.981

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > All Plugins
  3. Locate Royal Elementor Addons in the plugins list
  4. Check the current version number
  5. If version is below 1.3.981, click Update Now to upgrade to version 1.3.981 or later
  6. Verify the update completed successfully

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

Fix this in Royal Elementor Addons Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,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 $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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