dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2022-4708

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_save_template_conditions' AJAX action in versions up to, and including, 1.3.59. This allows any authenticated user, including those with subscriber-level permissions, to modify the conditions under which templates are displayed.

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 has a broken access control vulnerability in the 'wpr_save_template_conditions' AJAX action. The action lacks proper capability checks, allowing any authenticated user with subscriber-level permissions to modify template display conditions, potentially leading to unauthorized content manipulation.

MitigationUpdate Royal Elementor Addons to a version newer than 1.3.59. If immediate update is not feasible, implement custom capability checks (e.g., 'manage_options' capability) on the vulnerable AJAX action to restrict access to administrator-level users only.

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 and active
    Navigate to WordPress admin Dashboard > Plugins > Installed Plugins and locate 'Royal Elementor Addons' in the list. Verify the plugin status shows as 'Active'. Alternatively, query the wp_options table for option_name = 'active_plugins' and check if the plugin file is listed.
    Affected if The plugin is installed and active in WordPress.
  2. Identify the installed plugin version
    In the Plugins list page, click on the plugin name or view details to read the Version number from the plugin header. Alternatively, open the main plugin file (typically /wp-content/plugins/royal-elementor-addons/royal-elementor-addons.php) and read the Version header comment.
    Affected if The installed version is 1.3.59 or lower.
  3. Verify AJAX action endpoint exists
    Check if the vulnerable AJAX action 'wpr_save_template_conditions' is registered by examining the plugin source code for add_action('wp_ajax_wpr_save_template_conditions', ...). In a live environment, test if the endpoint responds at /wp-admin/admin-ajax.php?action=wpr_save_template_conditions.
    Affected if The AJAX action handler is present and accessible.
  4. Test subscriber-level user access
    Create or use a test user with the 'Subscriber' role. Attempt to make a POST request to /wp-admin/admin-ajax.php with action=wpr_save_template_conditions and verify if the request is processed rather than rejected. Check WordPress user roles in wp_users and wp_usermeta tables.
    Affected if A user with subscriber-level permissions can access and execute the AJAX action without receiving a capability error.

A user is affected if Royal Elementor Addons version 1.3.59 or lower is active and the wpr_save_template_conditions AJAX action permits access for subscriber-level authenticated users.

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 a version newer than 1.3.59. If immediate update is not feasible, implement custom capability checks (e.g., 'manage_options' capability) on the vulnerable AJAX action to restrict access to administrator-level users only.

Recommended fix Moderate confidence

1.3.60 or later (latest stable release)

  1. Verify current plugin version in WordPress admin under Plugins > Installed Plugins
  2. Navigate to Plugins > Add New > Upload Plugin (or check for update notification)
  3. Update Royal Elementor Addons to the latest available version (1.3.60 or higher)
  4. After updating, verify that the wpr_save_template_conditions AJAX action is no longer accessible to low-privileged users like subscribers

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