dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-2373

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-17
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 – Addons and Templates Kit for Elementor plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.7.1049 via the get_main_query_args() function due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract contents of non-public custom post types, such as Contact Form 7 submissions or WooCommerce coupons.

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 for WordPress contains an information exposure vulnerability in the get_main_query_args() function. This function fails to implement proper access controls, allowing unauthenticated attackers to query and extract sensitive data from non-public custom post types including Contact Form 7 submissions and WooCommerce coupons.

MitigationUpdate the Royal Addons for Elementor plugin to a version newer than 1.7.1049, or implement proper authentication and capability checks within the get_main_query_args() function to restrict access to authorized users only.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Addons for Elementor is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Royal Addons for Elementor' in the list, or check the wp-content/plugins directory for the royal-elementor-addons folder
    Affected if The plugin is present on the WordPress site
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Royal Addons for Elementor, and note the version number displayed below the plugin name. Alternatively, check the main plugin file header in wp-content/plugins/royal-elementor-addons/royal-addons-for-elementor.php for the 'Version' comment
    Affected if The version is 1.7.1049 or lower, or if the version cannot be determined but the plugin is installed on a potentially vulnerable version
  3. Check if the get_main_query_args AJAX action is exposed
    Inspect the plugin source code in wp-content/plugins/royal-elementor-addons/ for the get_main_query_args function, or test if the WordPress AJAX endpoint responds to requests calling this function. Search the plugin files for 'get_main_query_args' and verify the function exists and is hooked to wp_ajax or wp_ajax_nopriv
    Affected if The function is hooked to an unauthenticated AJAX action (wp_ajax_nopriv) without proper capability checks
  4. Verify sensitive custom post types are accessible
    Make an unauthenticated AJAX or REST API request that would trigger get_main_query_args and examine if it returns data from Contact Form 7 submissions (typically post type 'wpcf7_contact_form' or similar) or WooCommerce coupons (post type 'shop_coupon'). Check the response for coupon codes, discount amounts, or form submission data
    Affected if The plugin returns data from non-public custom post types such as WooCommerce coupons or Contact Form 7 submissions to unauthenticated users

The site is affected if Royal Addons for Elementor is installed with version 1.7.1049 or lower and the get_main_query_args function is accessible to unauthenticated users, allowing extraction of sensitive data from custom post types.

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

Update the Royal Addons for Elementor plugin to a version newer than 1.7.1049, or implement proper authentication and capability checks within the get_main_query_args() function to restrict access to authorized users only.

Recommended fix Moderate confidence

Version 1.7.1050 or later (any version above 1.7.1049)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Royal Addons for Elementor' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/royal-addons-for-elementor/ and upload manually
  6. 6. After updating, verify the plugin version is above 1.7.1049

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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