dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2022-4709

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_import_library_template' AJAX action in versions up to, and including, 1.3.59. This allows any authenticated user, including those with subscriber-level permissions, to import and activate templates from the plugin's template library.

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's 'wpr_import_library_template' AJAX action lacks proper capability verification, allowing any authenticated user with subscriber-level permissions or higher to import and activate arbitrary templates from the plugin's template library. This is a broken access control vulnerability where the AJAX endpoint trusts user authentication without validating authorization.

MitigationUpdate the Royal Elementor Addons plugin to version 1.3.60 or later, which implements proper capability checks on the affected AJAX action. Until patched, consider disabling the plugin or restricting AJAX access at the server level.

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
None

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

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
    Check your WordPress plugins directory or use wp-cli: wp plugin list --status=active --format=csv | grep -i 'royal elementor'
    Affected if Plugin is not found in your WordPress installation, you are not affected
  2. Identify the installed plugin version
    Navigate to WordPress admin > Plugins > Royal Elementor Addons, or run: wp plugin get royal-elementor-addons --field=version
    Affected if Version displayed is 1.3.59 or lower, you are likely affected
  3. Verify if the vulnerable AJAX endpoint responds to low-privilege requests
    As an authenticated user with subscriber role, send a POST request to /wp-admin/admin-ajax.php with action=wpr_import_library_template and check if the server returns a template import response rather than a 403 or capability error
    Affected if The AJAX endpoint returns a successful response for a subscriber-level user, you are affected
  4. Review user roles with subscriber-level access
    In WordPress admin, go to Users > All Users and check for any users assigned the Subscriber role, or run: wp user list --role=subscriber --field=user_login --format=count
    Affected if Any subscriber-level users exist and the plugin version is <=1.3.59, the vulnerability is exploitable in your environment

You are affected if Royal Elementor Addons version 1.3.59 or lower is installed AND any authenticated user with subscriber-level or higher permissions exists on your WordPress 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 a release after 1.3.59
Interim mitigation

Update the Royal Elementor Addons plugin to version 1.3.60 or later, which implements proper capability checks on the affected AJAX action. Until patched, consider disabling the plugin or restricting AJAX access at the server level.

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. If an update is available, click 'Update Now' to update to version 1.3.60 or later
  5. Alternatively, navigate to Dashboard > Updates and update the plugin from there
  6. After updating, verify that subscriber-level users can no longer access the wpr_import_library_template AJAX action

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-4709 — 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-4709 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