# CVE-2026-13756: WP Grid Builder <= 2.3.3 - Authenticated (Subscriber+) Privilege Escalation via 'key' Parameter

> Authenticated subscribers can escalate privileges to Administrator by exploiting missing authorization in the WP Grid Builder plugin's metadata REST endpoint.

- **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
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-9qvw-92r9-h632

## What is CVE-2026-13756?

CVE-2026-13756 is a high-severity vulnerability in WP Grid Builder, published on 11 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Grid Builder plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.3.3. This is due to missing authorization and meta key validation in the `update()` handler for the `/wp-json/wpgb/v2/metadata` REST endpoint. This makes it possible for authenticated attackers, with Subscriber-level access and above, to elevate their privileges to Administrator by updating their own `wp_capabilities` user meta with a crafted nested array payload.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-13756 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13756 is a high-severity vulnerability in WP Grid Builder, published on 11 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-13756 in the wild and no public exploit code.

Affected product: WP Grid 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-13756/ (Markdown: https://insights.sbomify.com/CVE-2026-13756/index.md)
```

## Sources

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

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