Elementor <= 3.13.1 - Missing Authorization to Settings Update
Strategic Overview
- Status
- Patched in 3.13.2
- Affected Plugin
- Elementor Website Builder – more than just a page builder
- Affected Version
<= 3.13.1- CVSS
- 5.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a medium-severity Missing Authorization vulnerability in the Elementor Website Builder WordPress plugin, affecting versions <= 3.13.1. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.13.2; sites on affected versions should update now. Disclosed May 2023.
Vulnerability Overview
The Elementor plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on the register_as_beta_tester(), ajax_enable_safe_mode(), ajax_get_category_items(), and ajax_re_migrate_globals() functions called via AJAX actions in versions up to, and including, 3.13.1. This makes it possible for authenticated attackers with minimal permissions such as subscribers to perform many actions such as registering the site for beta testing, enabling safe mode, remigrating globals and retrieving category items.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
Elementor Website Builder <= 3.13.1 carries this weakness at register_as_beta_tester(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Elementor Website Builder the fix is 3.13.2: builds <= 3.13.1 are affected, anything from 3.13.2 onward is not.
Remediation
Update to version 3.13.2, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Elementor Website Builder 3.13.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 8.8CVE-2022-1329: Elementor Website Builder 3.6.0 - 3.6.2 RCE
CVE-2022-1329 - 8.8CVE-2020-7055: Elementor Website Builder Arbitrary File Upload
CVE-2020-7055 - 8.8CVE-2017-18596: Elementor Website Builder Missing Authorization
CVE-2017-18596 - 6.5CVE-2023-47504: Elementor Website Builder Arbitrary Attachment Read
CVE-2023-47504
Other vulnerabilities in Elementor Website Builder – more than just a page builder
- 8.8CVE-2024-24934: Elementor Arbitrary File Deletion and PHAR
CVE-2024-24934 - 8.8CVE-2023-48777: Elementor <= 3.18.1 Arbitrary File Upload to RCE
CVE-2023-48777 - 7.2CVE-2020-7109: Elementor Website Builder <= 2.8.3 Cross-Site Scripting
CVE-2020-7109 - 6.6CVE-2023-0329: Elementor <= 3.12.1 SQL Injection
CVE-2023-0329 - 6.5CVE-2020-20634: Elementor Website Builder Authorization Bypass
CVE-2020-20634 - 6.4CVE-2026-6127: Elementor Website Builder <= 4.0.4 Stored XSS
CVE-2026-6127 - 6.4CVE-2025-14732: Elementor Website Builder <= 3.35.5 Stored XSS
CVE-2025-14732 - 6.4CVE-2026-32352: Elementor Website Builder <= 3.35.5 Stored XSS
CVE-2026-32352
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C