dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2022-4704

HIGH · 8.1 CVSS v3.1 Published 2023-01-10
Fix available
A fix is available. Upgrade to after 1.3.59 or later.
See remediation →
87/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
The Royal Elementor Addons plugin for WordPress is vulnerable to insufficient access control in the 'wpr_import_templates_kit' AJAX action in versions up to, and including, 1.3.59. This allows any authenticated user, including those with subscriber-level permissions, to import preset site configuration templates including images and settings.

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 lacks proper capability checks on the 'wpr_import_templates_kit' AJAX action. This allows any authenticated user with subscriber-level permissions (the lowest privilege level) to import site configuration templates, including images and settings, effectively giving them administrative-level access to site modification functionality.

MitigationUpdate the Royal Elementor Addons plugin to version 1.3.60 or later, which includes proper access control checks. Until then, consider disabling the affected AJAX endpoint or restricting user registration.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Royal Elementor Addons' in the list. Note the installed version number displayed there.
    Affected if The plugin is installed and the version listed is 1.3.59 or lower.
  2. Check plugin version against affected range
    Compare the installed version from the plugins page to the affected range: any version <= 1.3.59 is vulnerable.
    Affected if The installed version number is 1.3.59 or any lower version number.
  3. Verify AJAX endpoint is accessible
    Check if the 'wpr_import_templates_kit' AJAX action is registered and callable. This can be confirmed by examining the plugin files for the AJAX handler registration (look for 'wp_ajax_wpr_import_templates_kit' in the plugin code) or by testing if the endpoint responds to authenticated requests.
    Affected if The AJAX action 'wpr_import_templates_kit' is registered and accessible to any logged-in user.
  4. Review user role assignments
    In WordPress admin, go to Users > All Users and check which users exist and their assigned roles. Pay particular attention to any users with the 'Subscriber' role.
    Affected if There are user accounts with Subscriber-level permissions or any low-privilege role that can log in to the site.

You are affected if Royal Elementor Addons version 1.3.59 or lower is installed, the wpr_import_templates_kit AJAX endpoint is accessible, and there are user accounts (including subscribers) who can authenticate to WordPress.

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 access control checks. Until then, consider disabling the affected AJAX endpoint or restricting user registration.

Recommended fix Moderate confidence

Royal Elementor Addons version 1.3.60 or later

  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 the current version number to confirm it is 1.3.59 or earlier
  5. Click 'Update now' if an update is available, or manually download version 1.3.60 or later from wordpress.org/plugins/royal-elementor-addons
  6. After updating, verify the version number reflects the new version
  7. Test that the wpr_import_templates_kit AJAX action now properly restricts access to privileged users only

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-2022-4704 — 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-4704 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