# CVE-2026-110018: aBlocks <= 2.17.0 - Authenticated (Contributor+) Privilege Escalation to 'roleSlug' Block Attribute


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-j3rc-5xc4-8hjg

## What is CVE-2026-110018?

CVE-2026-110018 is a high-severity vulnerability in kodezen aBlocks – Gutenberg Blocks, User Dashboard Builder, Popup Builder, Form Builder & Animation Builder, published on 24 Oct 2026. 

### Official 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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-110018?


## How do I fix CVE-2026-110018?

No fix has been published for CVE-2026-110018 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110018 being exploited?

There is no known exploitation of CVE-2026-110018 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110018 and fix it if it is affected.

What it is: CVE-2026-110018 is a high-severity vulnerability in kodezen aBlocks – Gutenberg Blocks, User Dashboard Builder, Popup Builder, Form Builder & Animation Builder, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110018 in the wild and no public exploit code.

Affected product: kodezen aBlocks – Gutenberg Blocks, User Dashboard Builder, Popup Builder, Form Builder & Animation Builder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110018/ (Markdown: https://insights.sbomify.com/CVE-2026-110018/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110018
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110018
- OSV: https://osv.dev/vulnerability/CVE-2026-110018

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110018/
Summaries are generated and may contain mistakes; the official description above is the record.