CVE-2023-5360: WordPress Royal Elementor Plugin Zero-Day Fix

Learn about CVE-2023-5360, a critical zero-day vulnerability affecting over 200,000 WordPress websites that use the Royal Elementor Addons and Templates plugin. We cover risk assessment, technical details, and recommendations for mitigation.

Understanding CVE-2023-5360: The Zero-Day Vulnerability in WordPress's Royal Elementor Plugin

At a glanceCVE-2023-5360

CVE-2023-5360 has a CVSS 3.1 base score of 9.8 (Critical) from NVD. It is fixed in Royal-elementor-addons royal elementor addons 1.3.79.

Severity9.8 Critical (CVSS 3.1, NVD)
Fixed inRoyal-elementor-addons royal elementor addons 1.3.79
AffectedRoyal-elementor-addons royal elementor addons before 1.3.79
ExploitedNot in CISA's Known Exploited Vulnerabilities catalog
EPSS86% chance of exploitation in the next 30 days (FIRST, October 27, 2026)
Public exploitwpscan.com, wpscan.com · 8 GitHub repositories name it: proofs of concept, scanners, detections. Unverified: some are fake or malicious.
VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
WeaknessCWE-434
UbuntuListed, no packages yet
DebianListed, no packages yet
Red HatNot tracked yet

Is there a public exploit for CVE-2023-5360?

Public code exists as of October 28, 2026: NVD links 2 exploit references and 8 public GitHub repositories name it (proofs of concept, scanners and detections). It is not in CISA's Known Exploited Vulnerabilities catalog. None of it is verified: some such repositories are fake or carry malware, so read the code before running it, and only against systems you own. FIRST's EPSS puts the chance of exploitation in the next 30 days at 86%, higher than 99.7% of scored CVEs.

From NVD, Ubuntu, Debian · checked October 28, 2026

The security landscape for WordPress sites has always been a subject of critical importance, given the CMS's popularity. Recently, a significant zero-day vulnerability was discovered in a popular WordPress plugin called Royal Elementor Addons and Templates. In this article, we delve into the details of the CVE-2023-5360 vulnerability, its potential impact, and the recommendations for safeguarding your website.

Risk Scoring: Understanding the Threat Level

The CVE-2023-5360 vulnerability has received a Common Vulnerability Scoring System (CVSSv3) score of 9.8, signaling a critical level of risk. For context, the CVSS scale runs from 0 to 10, with higher numbers indicating greater severity. A score of 9.8 suggests that immediate action is required to mitigate the risks associated with this vulnerability.

Technical Details of the Vulnerability

The Royal Elementor Addons and Templates plugin, which boasts over 200,000 active installations, is essentially a tool that enables users to create web elements without needing coding skills. The vulnerability in question allows unauthenticated attackers to upload arbitrary files onto vulnerable websites. While the plugin does attempt to validate file extensions, it fails to properly sanitize user inputs, leading to potential remote code execution. Most payloads deployed in these attacks attempt to either create a new WordPress administrator user or act as a backdoor for the attackers.

Affected Products

The versions of Royal Elementor Addons and Templates that are vulnerable are all versions below 1.3.79. It's critical that users update their plugin to version 1.3.79 or later to mitigate the risks.

The State of Ongoing Attacks

According to security firms Wordfence and WPScan, this vulnerability has been actively exploited since August 30, 2023. Wordfence reported blocking over 46,000 attacks targeting this plugin, and WPScan has recorded 889 cases of distinct payloads being deployed post-exploitation, as of October 3, 2023.

Recommendations for Mitigation

Immediate Action

  1. Upgrade the Plugin: All users of this add-on should update to the latest version (1.3.79) as soon as possible.
  2. Run a Malware Scan: It’s recommended to run a scan using Wordfence CLI or the Wordfence plugin if you've been using the Royal Elementor Addons and Templates plugin.
  3. Free Scanning Solutions: In the absence of commercial solutions, free scanners are available to assess your website's vulnerability.
  4. Cleanup: Simply updating the plugin will not remove any existing malicious files or infections. A full website cleanup is necessary in such cases.

Long-term Measures

  1. Regular Software Updates: Keep all your WordPress plugins and themes up to date to reduce vulnerability.
  2. User Training: Educate administrators and content creators on how to recognize potential security threats and phishing attempts.
  3. Network Security: Utilize network security measures such as firewalls and intrusion detection systems to minimize risks.
  4. Incident Response Plan: Establish an incident response plan for quick action in case of future vulnerabilities.

Final Thoughts

This zero-day vulnerability in the Royal Elementor Addons and Templates plugin highlights the importance of maintaining updated security protocols for WordPress websites. It serves as a critical reminder that even popular plugins can contain severe vulnerabilities. Following the immediate action steps and long-term recommendations listed above can significantly reduce your site's risk profile.

#CVE-2023-5360#risk assessment#Royal Elementor Plugin#web security#Wordfence#WordPress Vulnerability#WPScan#Zero-Day Attack
Vishal
· Software & security engineer

Vishal writes Trickyworld's tutorials and interview-preparation guides on programming, databases, cyber security and AI. Vishal has been shipping production software long enough to have firm opinions about Python, PHP, Node.js, and JavaScript, and to have been wrong about each of them at least once. The work has run the whole stack: Drupal and Laravel applications, React front ends, MySQL and MongoDB underneath, Redis and Memcached for the things that had to be fast, Apache Solr for the things that had to be findable. That last part turned out to matter more than anyone expected. Tune a Solr index for a season, then watch a language model confidently retrieve the wrong document, and you recognise an old problem wearing new clothes. Most of what is hard about AI systems is not the model. It is retrieval, caching, latency budgets, and deciding what the system does when the answer comes back wrong — which is work he has been doing since well before anyone called it AI engineering. He plays a lot of games, which is less a hobby disclosure than an admission of where a good share of his engineering instinct came from. Real-time systems with a frame budget. State that has to stay coherent while a player does something no designer anticipated. The permanent question of what happens when the frame cannot finish in time. Those habits carry over more directly than they have any right to. He has written several books on programming, all built on the same conviction: most technical writing is unclear because the author never decided what to leave out. More from Vishal → · Editorial policy

More on Computer Tricks.

PHP

PHP Web Security Best Practices for Interview Preparation

Explore the vital PHP security practices including input validation, output escaping, and protection against SQL injection and XSS attacks. Whether you're an aspiring developer or preparing for an interview, this guide covers essential web security principles.

2 min read

Latest articles

$ subscribe --weekly

Get the next tutorial in your inbox.

Programming, security and AI — the practical bits, no spam. Unsubscribe any time.