dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2022-4702

MEDIUM · 6.5 CVSS v3.1 Published 2023-01-10
Fix available
A fix is available. Upgrade to after 1.3.59 or later.
See remediation →
71/100
Remediation priority · Elevated
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_fix_royal_compatibility' AJAX action in versions up to, and including, 1.3.59. This allows any authenticated user, including those with subscriber-level permissions, to deactivate every plugin on the site unless it is part of an extremely limited hardcoded selection. This also switches the site to the 'royal-elementor-kit' theme, potentially resulting in availability issues.

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_fix_royal_compatibility' AJAX action. This allows any authenticated user with subscriber-level permissions to arbitrarily deactivate plugins on the site (except a limited hardcoded set) and switch the site theme to 'royal-elementor-kit', causing availability issues.

MitigationUpdate the Royal Elementor Addons plugin to version 1.3.60 or later. Also audit user role capabilities and implement proper permission checks on AJAX actions.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Royal Elementor Addons version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Royal Elementor Addons'. The version is listed under the plugin name. Alternatively, check the plugin's main PHP file header or the readme.txt file in the plugin directory for the Version: field.
    Affected if The installed version is 1.3.59 or lower (any version <= 1.3.59 is affected).
  2. Verify the vulnerable AJAX action exists
    Inspect the plugin files (typically in wp-content/plugins/royal-elementor-addons/) for the function handling 'wpr_fix_royal_compatibility' AJAX action. Search the PHP files for this action name using grep or a code editor.
    Affected if The function 'wpr_fix_royal_compatibility' or 'wpr-fix-royal-compatibility' exists in the plugin code, indicating the vulnerable endpoint is present.
  3. Check for subscriber-level user accounts
    In WordPress admin, go to Users > All Users. Review the list for any users with the 'Subscriber' role. Check user capabilities in the Users panel or database wp_usermeta table for users with 'level_0' or 'subscriber' role capability.
    Affected if Any active user account with subscriber-level permissions exists on the site.
  4. Confirm theme 'royal-elementor-kit' is present
    Check the wp-content/themes/ directory for a folder named 'royal-elementor-kit' or 'royal-elementor-kit'. Also check the WordPress Themes panel to see if this theme is installed.
    Affected if The 'royal-elementor-kit' theme is installed on the site, making theme switching exploitation possible.

If the Royal Elementor Addons version is 1.3.59 or lower AND subscriber-level users exist on the site, the vulnerability is exploitable in your environment.

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. Also audit user role capabilities and implement proper permission checks on AJAX actions.

Recommended fix High confidence

Royal Elementor Addons 1.3.60 or later

  1. 1. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  2. 2. Locate 'Royal Elementor Addons' in the plugin list
  3. 3. If an update is available, click 'Update Now' to install the latest version
  4. 4. Verify the update was successful by checking the plugin version (should be 1.3.60 or higher)
  5. 5. Test that the site functions normally after the update

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