dbcve.org
Royal Elementor AddonsWordPress extension

CVE-2024-0516

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to 1.3.88 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 and Templates plugin for WordPress is vulnerable to unauthorized post metadata update due to a missing capability check on the wpr_update_form_action_meta function in all versions up to, and including, 1.3.87. This makes it possible for unauthenticated attackers to update certain metadata.

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 and Templates WordPress plugin has a broken access control vulnerability in the wpr_update_form_action_meta function, allowing unauthenticated attackers to update certain post metadata due to a missing capability check. This affects all versions up to and including 1.3.87.

MitigationUpdate the Royal Elementor Addons and Templates plugin to version 1.3.88 or later to receive the patch that adds proper capability validation to the affected function.

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.88

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Check installed plugin version
    Go to WordPress admin dashboard > Plugins > Royal Elementor Addons and Templates, or check the plugin header in wp-content/plugins/royal-elementor-addons/plugin.php for the 'Version' defined constant
    Affected if The installed version is 1.3.87 or lower (any version below 1.3.88)
  2. Verify wpr_update_form_action_meta function exists
    Inspect the plugin file wp-content/plugins/royal-elementor-addons/includes/classes/Actions.php (or similar location) and search for the function named 'wpr_update_form_action_meta'
    Affected if The function exists in the codebase, indicating the vulnerable code path is present
  3. Check AJAX action registration for the vulnerable function
    Search plugin files for 'wp_ajax_wpr_update_form_action_meta' or 'wp_ajax_nopriv_wpr_update_form_action_meta' - the latter allows unauthenticated access
    Affected if The AJAX action is registered with 'nopriv' prefix, allowing unauthenticated users to trigger the function
  4. Inspect capability check in the vulnerable function
    Examine the wpr_update_form_action_meta function body - look for 'current_user_can' or 'check_ajax_referer' calls at the beginning of the function
    Affected if No capability check (like current_user_can) is performed before updating post metadata, or the check is missing entirely

If the plugin version is 1.3.87 or lower AND the vulnerable AJAX action is exposed to unauthenticated users (nopriv), the environment is affected by this CVE.

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 1.3.88 or later
Fixed in 1.3.88
Interim mitigation

Update the Royal Elementor Addons and Templates plugin to version 1.3.88 or later to receive the patch that adds proper capability validation to the affected function.

Recommended fix High confidence

Royal Elementor Addons version 1.3.88 or later

  1. 1. Create a complete backup of your WordPress site (database and files) before applying any updates.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate 'Royal Elementor Addons and Templates' in the plugin list.
  4. 4. If an update is available, click 'Update Now' to install version 1.3.88 or later.
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin version shows 1.3.88 or higher under Plugins > Installed Plugins.
  7. 7. Test that your Elementor templates and forms continue to function correctly.

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-2024-0516 — 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-2024-0516 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