Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
8.8
CVE-2026-110018: aBlocks up to 2.17.0 lets contributors become editors
CVE-2026-110018 · published 29 days ago
Summary
The aBlocks plugin for WordPress (versions up to 2.17.0) allows any logged‑in user with Contributor rights to raise their account to an Editor level. This happens because a web request can change the user role without proper checks. Update the plugin to a newer version or remove the vulnerable feature until it is patched.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| kodezen | ablocks – gutenberg blocks, user dashboard builder, popup builder, form builder & animation builder | <= 2.17.0 |
Original advisory text
aBlocks <= 2.17.0 - Authenticated (Contributor+) Privilege Escalation to 'roleSlug' Block Attribute
The aBlocks – Gutenberg Blocks, User Dashboard Builder, Popup Builder, Form Builder & Animation Builder plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.17.0 via the `/ablocks/v1/form-builder/registration` REST endpoint. The vulnerability exists because the endpoint is registered with `permission_callback => __return_true` and the `register()` handler reads `roleSlug` directly from attacker-controlled block attributes in `post_content` without ever verifying that the block's `formType` is `registration` — a condition that `RegistrationFormSanitizer::verify()` imposes only at save-time, meaning a Contributor can preserve an arbitrary `roleSlug` by saving a block with `formType='login'` and then triggering the endpoint via a valid `wp_rest` nonce and post-ownership check. This makes it possible for authenticated attackers, with Contributor-level access and above, to escalate their WordPress role to Editor or any other non-administrator role and receive a fully authenticated session at the elevated privilege level via `WP_User::set_role()` and `wp_set_auth_cookie()`. Escalation is bounded below administrator-tier roles because `is_safe_registration_role()` rejects any role holding `manage_options`, `edit_users`, `delete_users`, `create_users`, `promote_users`, or `edit_theme_options`, meaning the highest practically reachable role on a standard WordPress installation is Editor.
References
- https://plugins.trac.wordpress.org/browser/ablocks/tags/2.16.0/includes/api/form...
- https://plugins.trac.wordpress.org/browser/ablocks/tags/2.16.0/includes/api/form...
- https://plugins.trac.wordpress.org/browser/ablocks/tags/2.16.0/includes/api/form...
- https://plugins.trac.wordpress.org/browser/ablocks/tags/2.16.0/includes/api/form...
- https://plugins.trac.wordpress.org/browser/ablocks/tags/2.16.0/includes/blocks/f...
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3756864%40ablocks&new...
- https://www.wordfence.com/threat-intel/vulnerabilities/id/6fe7efb5-540b-4d85-852...
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker full control
Type
CWE-269Improper Privilege Management
Timeline
Published24 Oct 2026
Updated22 Nov 2026
First seen24 Oct 2026
Track software like this
Free during beta