Royal Elementor Addons and Templates < 1.3.79 - Unauthenticated Arbitrary File Upload
Not confirmed exploited. 1 of 8 rule sources name it. Our CRS test: not blocked.
The Royal Elementor Addons and Templates WordPress plugin before 1.3.79 does not properly validate uploaded files, which could allow unauthenticated users to upload arbitrary files, such as PHP and achieve RCE.
Edge coverage
Claimed by vendorsAsk Vigil
AI · answers from this pageWorkers AI (Llama 3.3). Can be wrong: check the cited source.
Public exploits
3 found- MetasploitWordPress Royal Elementor Addons RCE2023-11-23 · exploit · rank Excellent · has check
- Exploit-DBRoyal Elementor Addons and Templates 1.3.78 - Unauthenticated Arbitrary File Upload2025-04-05 · webapps · multiple
- NucleiCVE-2023-5360.yamldetection template, replayed in our lab
Links are to third-party code: never run it outside an isolated lab.
Timeline
- 2023-10-31CVE publishedCVE List
- 2023-11-23Metasploit module publishedWordPress Royal Elementor Addons RCE
- 2025-04-05Exploit published on Exploit-DBRoyal Elementor Addons and Templates 1.3.78 - Unauthenticated Arbitrary File Upload
- 2025-12-03F5 ships a ruleWordPress Royal Elementor Arbitrary File Upload
- 2026-11-02Our test: OWASP Core Rule Set let it throughparanoia level 1, anomaly threshold 5, default CRS settings
- 2026-11-02Our test: OWASP Core Rule Set let it throughparanoia level 2, anomaly threshold 5, default CRS settings
Vendor statements
QuotedCloudflareWAF Managed Rules
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
AWSAWS WAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.
Microsoft AzureFront Door and Application Gateway WAF (DRS)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.
Google CloudCloud Armor preconfigured WAF rules
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
FastlyNext-Gen WAF virtual patches
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
F5Attack signatures (Distributed Cloud WAF)
First rule 2025-12-03, 764 days after the CVE was published.
Added: signature 200020230 "WordPress Royal Elementor Arbitrary File Upload" (Malicious File Upload, risk High), systems: WordPress. References: CVE-2023-5360.
AkamaiApp & API Protector (Adaptive Security Engine)
This vendor publishes no machine-readable rule changelog we can check.
OWASP CRSCore Rule Set (open source, used inside many WAFs)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.
Social
No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.