Royal Elementor Addons Flaw: What to Do Now
If your WordPress site runs Royal Elementor Addons version 1.7.1068 or older, update the plugin to a newer version today (or remove it if no newer version exists), because CVE-2026-111851 is a high-severity code injection flaw.
This post is for owners of WordPress and Elementor sites who want to know, without the jargon, whether this affects them and what to do. You will get a plain explanation of the flaw, a quick way to check your version, exact update steps (dashboard and command line), and a short checklist to confirm your site looks clean afterward.
What is the Royal Elementor Addons vulnerability?
Royal Elementor Addons is a WordPress plugin that adds extra widgets and design options to the Elementor page builder. A flaw tracked as CVE-2026-111851 was published on 2026-10-22. A CVE is just a public ID number so everyone can talk about the same bug.
The record describes it as 'unsafe reflection' (a weakness type called CWE-470) that allows code injection. In plain English: the plugin lets outside input help decide which piece of code the site runs. If a person can control that input, they may be able to make your site run code you never intended.
The affected range is every version from the start of the plugin through 1.7.1068. The record does not list a fixed version, so the safe move is to update to the newest version available and check the vendor's changelog.
How serious is it?
The record rates it High, with a CVSS score of 7.6 out of 10. CVSS is a standard scoring system for how bad a bug is. The vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H breaks down like this (CVSS 3.1 specification):
| Part | Value | What it means for you |
|---|---|---|
| AV:N | Network | It can be attempted over the internet. The attacker does not need to be near your server. |
| AC:L | Low complexity | No special conditions or luck are needed. |
| PR:L | Low privileges | The attacker needs a basic logged-in account first. |
| UI:N | No user interaction | You or your staff do not have to click anything. |
| S:U | Unchanged scope | The impact stays within the WordPress site itself. |
| C:L / I:L | Low | Limited exposure and limited changes to data. |
| A:H | High | The biggest rating is for availability, meaning the site could be knocked offline or broken. |
The low-privileges part matters. It suggests an attacker would need some kind of account, such as a subscriber, customer or contributor login. If your site lets anyone register, that bar is easy to clear. If only you and your team have accounts, the risk is lower, but you should still update.
Two honest notes. First, NVD lists this entry as 'Deferred', which means it has not yet done its own full analysis, so the record is thin. Second, the Patchstack database entry referenced by NVD labels it an arbitrary code execution issue. The NVD record and the Patchstack entry do not say whether this bug is being used in real attacks, and we will not guess. Treat it as 'patch promptly', not 'panic'.
Who is affected?
You are affected if all of these are true:
- Your site runs WordPress.
- The plugin Royal Elementor Addons (folder name
royal-elementor-addons) is installed. Update it even if it is deactivated, because the files are still on your server. A deactivated plugin is less likely to be exploitable, but delete it if you do not use it. - Its version is 1.7.1068 or lower.
If you also use a paid or Pro version of the plugin, check the vendor's own documentation and changelog for how it is updated. The NVD record only names the plugin above.
How to check your version
- Log in to WordPress.
- Go to Plugins > Installed Plugins.
- Find Royal Elementor Addons. The version number appears under the plugin name.
If you have command-line access with WP-CLI, this prints the version and whether an update is waiting:
wp plugin list --name=royal-elementor-addons --fields=name,status,version,update
Anything at or below 1.7.1068 needs action.
How to update Royal Elementor Addons
Updating to a newer release is the fix, once one exists. It usually takes a few minutes.
- Back up first. Use your host's backup tool or a plugin you already trust. Make sure it covers both files and the database.
- Go to Dashboard > Updates or Plugins > Installed Plugins.
- Next to Royal Elementor Addons, click Update now.
- If no update button appears, click Check Again on the Updates page. You can also download the latest version from the plugin's page on wordpress.org and upload it with Plugins > Add New > Upload Plugin.
- Open the plugin's changelog (on its wordpress.org page, under the Development tab) and confirm the latest version is newer than 1.7.1068. The changelog may or may not mention a security fix, so do not treat a missing note as a sign the update is unsafe.
If the newest version is still 1.7.1068 or lower, no fix is available yet. Deactivate and delete the plugin until the vendor publishes a newer release, and replace its widgets with another option.
- Visit your key pages (home, contact form, checkout) and make sure nothing looks broken. Clear any cache plugin afterward.
With WP-CLI, the update is one line:
wp plugin update royal-elementor-addons
If the update breaks a page layout, do not roll back to the old version and leave it. Restore your backup on a staging copy, or ask your developer for help. Staying on a vulnerable version is the worse trade.
What if you cannot update right now?
Sometimes a custom design depends on the plugin and you need time. Short-term steps that reduce risk:
- Deactivate and delete the plugin if you are not actively using its widgets.
- Turn off open sign-ups. Go to Settings > General and untick 'Anyone can register' if you do not need it. This limits who can get the low-level account the flaw seems to require. If you run WooCommerce or a membership plugin, also check its own account-registration settings, since those can still create logged-in accounts.
- Remove old accounts under Users that nobody recognizes or needs.
- Ask your host whether they offer a firewall rule for this plugin. Treat that as a stopgap, not a fix.
How to check your site for signs of trouble
The sources we were given do not say this bug is being exploited. Still, if you ran a vulnerable version for a while, a quick check is cheap. Look for these:
- [ ] New administrator users you did not create. With WP-CLI:
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered - [ ] Changed core files. Run
wp core verify-checksums, which compares WordPress core files against the official ones. - [ ] Changed plugin files. Run
wp plugin verify-checksums --all. Plugins that are not hosted on wordpress.org may be skipped. - [ ] Unfamiliar plugins, or files in
wp-content/uploadsending in.php(uploads should hold images and documents, not code). - [ ] Unexpected redirects, spam pages, or a warning from Google or your host.
- [ ] Your hosting dashboard showing odd traffic spikes or unexplained slowdowns.
If anything on that list looks wrong, stop and read our website hacked guide before changing more things, so you do not wipe useful evidence. Change your passwords (WordPress, hosting, database) after cleanup, not before.
Why plugin bugs like this keep happening
WordPress itself is maintained carefully. Third-party plugins are a common way WordPress sites get into trouble, because there are tens of thousands of them and many are small codebases run by small teams. Page-builder add-ons can be a place for bugs, since they handle a lot of user-controlled input.
You cannot avoid plugins altogether. You can keep the list short, remove what you do not use, turn on automatic updates for plugins you trust (Plugins > Installed Plugins > Enable auto-updates), and check your site from the outside. Our free website security check is a quick passive look at your domain, and the is my website hackable guide explains what attackers usually look for first.
Key takeaways
- CVE-2026-111851 is a high-severity (CVSS 7.6) code injection flaw in Royal Elementor Addons, affecting versions through 1.7.1068.
- Update to the latest version now, and confirm it is newer than 1.7.1068. No fixed version is listed in the NVD record. If the newest version is still 1.7.1068 or lower, deactivate and delete the plugin until a newer release is published.
- The score suggests an attacker needs a basic account, so closing open registration (and checking WooCommerce or membership sign-up settings) and removing unused users helps.
- After updating, check for unknown admin users, changed files and strange redirects. The sources we were given do not say this is being exploited, but the check takes ten minutes.
- Delete plugins you do not use and turn on auto-updates for the ones you trust.
Want a human to look at your site?
Updating fixes this one bug. It does not tell you whether something else on your site is weak. A Bug Circuit audit is a manual test of one website by a real security engineer, ending in a written report with every issue, its severity, the evidence and the fix steps. The Essential plan is $49 one-time, and you can see the details on the pricing page. It is a focused small-site audit, not a compliance certificate or a multi-week enterprise pentest. We report problems and explain the fix. If you want us to do the fixing, that is a separate service we quote first.
A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.
See pricing