Royal Addons for Elementor – Addons and Templates Kit for Elementor Vulnerability (CVE-2026-17585)

On this page

Security Alert Summary

A vulnerability in the Royal Addons for Elementor – Addons and Templates Kit for Elementor plugin (CVE-2026-17585) can allow unauthenticated attackers to extract arbitrary postmeta values from published posts by abusing a frontend-search parameter. The issue is rooted in a publicly exposed nonce and an insecure substring-matching mechanism that can be driven over the network without user interaction.


CVE Details

  • CVE ID: CVE-2026-17585
  • Affected component: Royal Addons for Elementor – Addons and Templates Kit for Elementor (plugin)
  • Affected versions: All versions up to and including 1.7.1066
  • Published: September 12, 2026 at 08:16:23 AM
  • Last modified: September 12, 2026 at 08:16:23 AM
  • CVSS v3.1: Base score 5.3 (MEDIUM) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
  • Attack vector / complexity: Network / Low
  • Authentication / privileges / user interaction: Authentication: None; Privileges required: None; User interaction: None
  • Primary impact: Confidentiality: Low (exposure of postmeta data); Integrity: None; Availability: None
  • Weakness: CWE-200 (Sensitive Information Exposure)

Technical Details

The plugin exposes a search-related parameter, wpr_keyword, that can be used to perform character-by-character substring matching against entries in the wp_postmeta table. An attacker can iterate queries to recover arbitrary postmeta values from published posts.

The exploitability is increased because the required nonce is emitted publicly via wp_localize_script on any frontend page that loads a Royal Elementor widget. Because the nonce is available on public pages, an attacker does not need an authenticated session or prior interaction to obtain it and drive the requests.

The practical result is disclosure of postmeta content accessible to these AJAX/search routines. The description identifies the vulnerable parameter and the public nonce emission as the root causes; no additional functions or endpoints are named in the provided data.


How This Could Impact Your Website

Consider a WordPress site with multiple users: a site owner, internal staff who create and manage content, and an external contractor who contributes posts or custom fields. If sensitive data such as internal email addresses, API keys stored in postmeta, or other private attributes are kept in postmeta fields, an unauthenticated attacker could extract parts or all of those values using the described substring technique.

Realistic consequences include exposure of internal user email addresses and an increased risk of targeted phishing or social engineering against staff or contractors. The impact aligns with the reported confidentiality impact (Low) and does not imply forced privilege escalation or full site takeover based on the provided details.

If you\’re unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review.


Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, particularly for contributor-level accounts and external contractors.
  • Enforce strong passwords and enable two-factor authentication for editor and administrator accounts.
  • Remove unused or unmaintained plugins and themes from the site.
  • Monitor site activity and logs for unusual behavior or repeated automated requests to search/ajax endpoints.

If you\’d like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References