dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-4024

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Addons for Elementor plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `wpr_update_form_action_meta` AJAX action in all versions up to, and including, 1.7.1056. The handler is registered on both `wp_ajax` and `wp_ajax_nopriv` hooks, making it accessible to unauthenticated users. Although a nonce is verified, the nonce (`wpr-addons-js`) is publicly exposed in frontend JavaScript via `WprConfig.nonce` on any page that loads Royal Addons widgets, rendering the protection ineffective. The endpoint also lacks any capability or ownership checks and directly calls `update_post_meta()` with user-controlled input on a whitelisted set of form action meta keys. This makes it possible for unauthenticated attackers to modify form action configuration metadata (email, submissions, Mailchimp, and webhook settings) on any post, potentially leading to webhook/email action tampering and data exfiltration via modified webhook URLs.

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 Addons for Elementor plugin has an insecure AJAX endpoint (`wpr_update_form_action_meta`) accessible to unauthenticated users due to registration on `wp_ajax_nopriv`. While a nonce is checked, it is exposed in frontend JavaScript via `WprConfig.nonce`, making it trivially circumvenible. The endpoint directly calls `update_post_meta()` with user-controlled input on any post without capability or ownership validation, allowing unauthenticated attackers to modify form action settings (email, Mailchimp, webhooks).

MitigationReplace the publicly-exposed nonce with server-side only validation, add proper capability checks (e.g., `edit_post` with ownership verification), and remove the endpoint from unauthenticated hooks or implement robust authorization before allowing metadata modifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Confirm Royal Addons for Elementor is installed
    Check for the plugin in wp-content/plugins/ directory or query the WordPress plugins database table for 'royal-addons-for-elementor'
    Affected if Plugin is installed and active
  2. Check the installed Royal Addons version
    Inspect the plugin main file header or query the WordPress options table for the active version, then compare against known affected version range
    Affected if Version falls within the vulnerable range (prior to patch)
  3. Verify the AJAX endpoint is accessible to unauthenticated users
    Check the plugin code for add_action('wp_ajax_nopriv_wpr_update_form_action_meta') or equivalent hook registration exposing the endpoint without login requirement
    Affected if The endpoint is hooked to wp_ajax_nopriv, allowing unauthenticated access
  4. Confirm nonce exposure in frontend JavaScript
    Search plugin code for WprConfig.nonce being echoed to frontend or inspect page source for nonce value in JavaScript variable exposing it publicly
    Affected if The nonce is accessible in client-side JavaScript (WprConfig object)
  5. Verify lack of capability and ownership validation
    Review the wpr_update_form_action_meta AJAX handler code to confirm it lacks current_user_can('edit_post', $post_id) checks and ownership verification before calling update_post_meta()
    Affected if No capability checks or post ownership validation are performed before metadata updates

If Royal Addons for Elementor is installed with a vulnerable version and the AJAX endpoint is exposed to unauthenticated users with a client-side nonce, the environment is affected by CVE-2026-4024.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace the publicly-exposed nonce with server-side only validation, add proper capability checks (e.g., `edit_post` with ownership verification), and remove the endpoint from unauthenticated hooks or implement robust authorization before allowing metadata modifications.

Recommended fix Moderate confidence

Royal Addons for Elementor version newer than 1.7.1056 (check WordPress plugin repository for latest fixed release)

  1. Check the current installed version of Royal Addons for Elementor plugin
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. If the installed version is 1.7.1056 or below, update Royal Addons to the latest available version from the WordPress plugin repository
  4. After updating, verify the new version number reflects the update
  5. Test that AJAX functionality for form actions still works correctly for authorized users
Caveat Review plugin changelog for any breaking changes between current and new version before updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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