dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2022-4701

HIGH · 8.8 CVSS v3.1 Published 2023-01-10
Fix available
A fix is available. Upgrade to after 1.3.59 or later.
See remediation →
94/100
Remediation priority · Urgent
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
The Royal Elementor Addons plugin for WordPress is vulnerable to insufficient access control in the 'wpr_activate_required_plugins' AJAX action in versions up to, and including, 1.3.59. This allows any authenticated user, including those with subscriber-level permissions, to activate the 'contact-form-7', 'media-library-assistant', or 'woocommerce' plugins if they are installed on the site.

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 WordPress plugin fails to enforce proper authorization on the wpr_activate_required_plugins AJAX action, allowing any authenticated user (including subscriber-level) to activate specific plugins (contact-form-7, media-library-assistant, woocommerce) already installed on the site. This is a broken access control vulnerability where the plugin relies on client-side requests without server-side capability verification.

MitigationUpdate Royal Elementor Addons to version 1.3.60 or later which implements proper admin capability checks on the affected AJAX action. Until patched, monitor user activity logs for unauthorized plugin activation attempts.

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

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Royal Elementor Addons plugin is installed
    Go to WordPress admin > Plugins and look for 'Royal Elementor Addons' in the installed plugins list, or query the wp_plugins database table for this plugin slug
    Affected if The plugin appears in the installed plugins list and is active
  2. Check installed version of Royal Elementor Addons
    In WordPress admin > Plugins, find Royal Elementor Addons and note the version number displayed, or query wp_options for option_name 'wpr_addons_version'
    Affected if The installed version is 1.3.59 or lower
  3. Confirm plugin is active
    Check the plugin status in WordPress admin > Plugins - the plugin must be both installed AND active for the vulnerability to be exploitable
    Affected if The plugin shows as 'Active' status
  4. Review user role assignments
    Check WordPress Users panel for any subscriber-level or low-privilege accounts that should not exist, or query wp_usermeta for users with subscriber role (wp_capabilities = a:1:{s:10:"subscriber"})
    Affected if There are authenticated user accounts (any role) present in the system
  5. Audit recent plugin activation events
    Check WordPress activity logs, server logs, or database for unexpected activation of plugins contact-form-7, media-library-assistant, or woocommerce that were not initiated by administrator actions
    Affected if These specific plugins show activation timestamps that do not correspond to legitimate admin actions

A user is affected if Royal Elementor Addons version 1.3.59 or lower is installed and active on the WordPress site, allowing any authenticated user to activate specified plugins without proper authorization checks.

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 a release after 1.3.59
Interim mitigation

Update Royal Elementor Addons to version 1.3.60 or later which implements proper admin capability checks on the affected AJAX action. Until patched, monitor user activity logs for unauthorized plugin activation attempts.

Recommended fix High confidence

Royal Elementor Addons version 1.3.60 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Royal Elementor Addons' in the plugin list
  4. Click 'Update now' if an update is available, or manually update by uploading the latest version from wordpress.org/plugins/royal-elementor-addons/
  5. Verify the update was successful by confirming the version number is above 1.3.59

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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