dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2022-4703

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_reset_previous_import' AJAX action in versions up to, and including, 1.3.59. This allows any authenticated user, including those with subscriber-level permissions, to reset previously imported data.

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 fails to enforce proper authorization on the wpr_reset_previous_import AJAX action, allowing any authenticated user with subscriber-level permissions or higher to reset previously imported template data. This broken access control vulnerability enables low-privilege users to perform an administrative function.

MitigationUpdate the Royal Elementor Addons plugin to version 1.3.60 or later, which implements proper capability checks on the affected AJAX action.

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 plugin is installed
    Navigate to WordPress admin > Plugins and locate Royal Elementor Addons, or check the plugin files in wp-content/plugins/royal-elementor-addons/ for the main PHP file and look for the 'Version' header comment
    Affected if The plugin is installed and active in WordPress
  2. Identify the installed plugin version
    Read the Version field from the plugin page in WordPress admin, or open the main plugin PHP file and locate the 'Version:' header in the plugin comment block
    Affected if The installed version is 1.3.59 or lower (any version <= 1.3.59)
  3. Verify the vulnerable AJAX action exists in the plugin
    Inspect the plugin PHP files, searching for 'wpr_reset_previous_import' to confirm the vulnerable AJAX action handler is present in the codebase
    Affected if The AJAX action wpr_reset_previous_import is defined in the plugin code
  4. Confirm the site has user accounts with subscriber-level access
    In WordPress admin > Users, review existing user accounts and their assigned roles; subscriber is the lowest privilege role in WordPress
    Affected if There is at least one user account with the Subscriber role (or any role ranked Subscriber or higher, including Contributor, Author, Editor, or Administrator)
  5. Test AJAX action accessibility (optional technical check)
    If you have a test environment, send a crafted POST request to /wp-admin/admin-ajax.php with action=wpr_reset_previous_import while authenticated as a low-privilege user (subscriber); examine the response for successful execution versus authorization failure
    Affected if The AJAX action executes without returning a permission denied or capability check error, indicating the vulnerability is present

A user is affected if Royal Elementor Addons version 1.3.59 or lower is installed, the site has at least one subscriber-level user account, and the wpr_reset_previous_import AJAX action is accessible to that user without proper authorization 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 implements proper capability checks on the affected AJAX action.

Recommended fix High 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. Locate Royal Elementor Addons in the plugin list
  4. Check if an update is available (version 1.3.60 or higher)
  5. If an update is available, click 'Update Now' to install the fixed version
  6. After updating, verify the plugin version shows 1.3.60 or later in the plugins list

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 / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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