dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2022-4700

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_theme' 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 'royal-elementor-kit' theme. If no such theme is installed doing so can also impact site availability as the site attempts to load a nonexistent theme.

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 versions up to 1.3.59 has a broken access control vulnerability in the 'wpr_activate_required_theme' AJAX action. The function lacks capability checks, allowing any authenticated user with subscriber-level permissions to activate the 'royal-elementor-kit' theme, which normally requires administrator-level privileges.

MitigationUpdate the Royal Elementor Addons plugin to version 1.3.60 or later which includes proper capability validation for the affected AJAX action. Until updated, consider disabling the plugin if site availability is critical.

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. Confirm Royal Elementor Addons plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Royal Elementor Addons' in the installed plugins list, or check the plugins directory for the plugin files
    Affected if The plugin is installed and active
  2. Identify installed plugin version
    In WordPress admin > Plugins > Royal Elementor Addons, view the plugin details to see the version number displayed
    Affected if Version is 1.3.59 or lower
  3. Verify AJAX action accessibility
    Check if the WordPress REST API or admin-ajax.php endpoint responds to the 'wpr_activate_required_theme' action. This can be tested by attempting a POST request to /wp-admin/admin-ajax.php with action=wpr_activate_required_theme while logged in as a subscriber-level user
    Affected if The AJAX action executes without returning a capability error for subscriber-level users
  4. Check for existing subscriber accounts
    In WordPress admin > Users, review the user list to see if any users with 'Subscriber' role exist on the site
    Affected if Subscriber-level accounts exist on the site
  5. Confirm theme activation capability exposure
    Attempt to access or trigger the theme activation function via the vulnerable AJAX endpoint using a low-privilege account. If the theme 'royal-elementor-kit' can be activated without administrator privileges, the vulnerability is present
    Affected if Non-administrator users can activate the royal-elementor-kit theme

The site is affected if Royal Elementor Addons version 1.3.59 or lower is installed, the plugin is active, and subscriber-level users can access the wpr_activate_required_theme AJAX action to activate themes without proper capability 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 the Royal Elementor Addons plugin to version 1.3.60 or later which includes proper capability validation for the affected AJAX action. Until updated, consider disabling the plugin if site availability is critical.

Recommended fix High confidence

Royal Elementor Addons version 1.3.60 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Dashboard > Updates or Plugins > All Plugins.
  3. 3. Check for updates to the Royal Elementor Addons plugin.
  4. 4. If an update is available, update the plugin to version 1.3.60 or later.
  5. 5. After updating, verify that the plugin functions correctly and the vulnerability is remediated.

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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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