The short version
- The flaw. Elementor versions 4.3.0 and 4.3.1 bypass WordPress REST nonce validation whenever the string elementor/v1/events/ appears anywhere in the request URI, including the query string an attacker writes. A logged-in administrator who opens a crafted link carries out any REST API action their account is permitted to perform.
- The result. On a default installation the action creates a second administrator account controlled by the attacker, allowing the attacker to take control of the site. The flaw carries a CVSS score of 8.8 out of 10; no CVE identifier has been assigned.
- Who is exposed. Elementor is active on more than 10 million WordPress sites, and WordPress.org statistics put installations of the two affected versions at more than 2 million. Earlier Elementor releases do not contain the affected module, though some of them are vulnerable to other flaws that are already being exploited.
- The fix. Elementor released version 4.3.2, which stops the bypass through the query string. Patchstack reported the issue to Elementor on 22 September after receiving it from researcher Saggre; the fix followed two days later.
Timeline
| Date | Event |
|---|---|
| 22 Sep | Patchstack reports the flaw to Elementor after receiving it from researcher Saggre. |
| 24 Sep | Elementor releases version 4.3.2 with a fix, two days after the report. |
| 25 Sep | BleepingComputer publishes an article citing Patchstack's analysis of the flaw. |
How the bypass works
Elementor's Editor Events module checks the raw request URI for the elementor/v1/events/ path. When that string is present, the module skips the nonce check that WordPress normally applies to cookie-authenticated REST API requests. Because the query string counts as part of the URI and is chosen by whoever composes the link, any REST request can exempt itself by appending a harmless-looking parameter.
The exemption covers the whole REST API surface of a site, WordPress core routes and those of every other installed plugin included. Patchstack's example targets the users endpoint to create an administrator account. The attack needs no JavaScript, no submitted form and no page under the attacker's control; a plain link in an email, chat message or site comment is enough. Patchstack put the mechanism plainly: "One link, opened by a logged-in WordPress user, makes that user carry out any REST API action their account is permitted to perform."
Who is affected
Only versions 4.3.0 and 4.3.1 carry the flaw. Elementor is one of the most widely installed WordPress plugins, present on over 10 million sites, and the affected releases alone account for up to 2 million sites according to WordPress.org figures cited by BleepingComputer, while The Hacker News reports more than 2 million installations.
Sites on Elementor releases before 4.3.0 are not exposed to this bypass because they do not include the Editor Events proxy. That does not make those older releases safe: the sources note they are vulnerable to other flaws, some of which are already being exploited in the wild.
Disclosure and fix
The researcher credited as Saggre found the bug and passed it to Patchstack, which reported it to Elementor on 22 September. Elementor shipped version 4.3.2 two days later; BleepingComputer and The Hacker News published their reports at the end of that week. No CVE identifier had been assigned when the reports were published, and the flaw carries a CVSS score of 8.8.
The two source reports differ only slightly in framing: one describes the bug as affecting cookie-authenticated REST requests, the other as affecting a logged-in administrator who follows a link.
What is not known yet
- Whether anyone exploited the flaw against 4.3.0 or 4.3.1 sites before the fix shipped, and how many sites, if any, received an attacker-created administrator account.
- Who is behind any exploitation, and whether any activity has been observed in the wild at all.
- How many of the affected installations had been updated to 4.3.2 by the time the reports were published.
- Why no CVE identifier had been assigned at the time of disclosure.
What to do
If you use Elementor
- Update the plugin to version 4.3.2, which closes the query-string bypass.
- List your administrator accounts and remove any you do not recognise, checking the email address and creation date on each.
- Check your site logs for POST requests to the users endpoint that carry a query parameter containing elementor/v1/events/.
If you run WordPress sites for an organisation
- Inventory every site running Elementor 4.3.0 or 4.3.1 and patch them first.
- Schedule the same update for sites on older Elementor releases, which carry other flaws, some already exploited.
- Tell site administrators not to follow unexpected links while logged in, since the session does the work.
For everyone else
- Treat any authenticated browser session as a target: a single link opened by a privileged user can perform actions with that user's rights, so least-privilege accounts and prompt patching of plugins are the controls that limit the damage.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.