dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2022-4707

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 →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Cross-Site Request Forgery in versions up to, and including, 1.3.59. This is due to missing nonce validation in the 'wpr_create_mega_menu_template' AJAX function. This allows unauthenticated attackers to create Mega Menu templates, granted they can trick an administrator into performing an action, such as clicking a link.

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 WordPress plugin fails to validate nonces in its wpr_create_mega_menu_template AJAX function. This allows unauthenticated attackers to craft malicious requests that trick authenticated administrators into creating arbitrary Mega Menu templates via cross-site request forgery. The lack of CSRF tokens enables social engineering attacks where an administrator clicks a malicious link.

MitigationUpdate the Royal Elementor Addons plugin to version 1.3.60 or later, which includes proper nonce validation for the affected AJAX function. As a defensive measure, ensure administrators are trained to avoid clicking untrusted links.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify Royal Elementor Addons is installed
    Access WordPress admin plugins page or check wp-content/plugins directory for the royal-elementor-addons folder
    Affected if The plugin folder royal-elementor-addons exists in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Royal Elementor Addons and view the version number, or read the main plugin file header for the Version field
    Affected if The reported version is 1.3.59 or lower (any version up to and including 1.3.59)
  3. Confirm AJAX endpoint exists
    Check if the WordPress site responds to wp-admin/admin-ajax.php?action=wpr_create_mega_menu_template (this is a passive check; do not send requests)
    Affected if The AJAX action wpr_create_mega_menu_template is registered and accessible
  4. Inspect nonce validation in source code
    Review the PHP file containing the wpr_create_mega_menu_template callback function (typically in includes/ajax.php or similar) and look for nonce verification calls such as check_ajax_referer, wp_verify_nonce, or wp_create_nonce before processing the request
    Affected if The function lacks nonce validation checks or uses an improper nonce verification method

You are affected if Royal Elementor Addons version 1.3.59 or earlier is installed and the wpr_create_mega_menu_template AJAX function is present without proper nonce validation in its code.

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 nonce validation for the affected AJAX function. As a defensive measure, ensure administrators are trained to avoid clicking untrusted links.

Recommended fix Moderate confidence

1.3.60 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Royal Elementor Addons
  4. Check if an update is available and update to the latest version (1.3.60 or later)
  5. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. Verify the update was successful by checking the plugin version

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