Skip to content
EXYS
Back to the CVEs

CVE-2026-110018

8.8, high

Kodezen aBlocks - Gutenberg Blocks, User Dashboard Builder, Popup Builder, Form Builder & Animation Builder Improper Privilege…

NVD (opens in a new tab) CVE.org (opens in a new tab)
CVSS
8.8, high high CVSS v3.1
EPSS, next 30 days
n/a
Exploitation
No public evidence
Published
24 Oct 2026yesterday

Description

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.

Details

Vendor
Kodezen
Product
aBlocks - Gutenberg Blocks, User Dashboard Builder, Popup Builder, Form Builder & Animation Builder
Weakness
CWE-269 (opens in a new tab)
Status
Received
Updated
24 Oct 2026
Assigner
security@wordfence.com

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References 7

Other references 7

The kind is read from NVD's tags where present and from the shape of the URL otherwise, so treat it as a hint.

Beyond this page

Is CVE-2026-110018 in your network?

This page tells you how dangerous CVE-2026-110018 is out there. Whether it sits on one of your devices, only a scan of your own network can tell. That is what our systems do, every day, for the companies we protect.

  • EXYS7600 OCELOT

    Find it before attackers do

    Ocelot scans your network on a schedule and reports every vulnerability it finds by its CVE identifier, with its CVSS score and how many of your hosts are affected. A finding like CVE-2026-110018 comes with the devices to patch.

    Learn more about EXYS7600 OCELOT

  • EXYS7950 KONDRA

    Detect it if it's exploited

    Until the patch is applied, Kondra monitors your network, events and endpoints in real time. It keeps an inventory of the software installed on every endpoint, and its anomaly detection rules flag what an attacker does once inside.

    Learn more about EXYS7950 KONDRA
Check your exposure

Assembled from the NVD 2.0 API, the CISA Known Exploited Vulnerabilities Catalog and FIRST EPSS. Scores are as of our last collection on 25 Oct 2026, not the live upstream state.