# CVE-2026-118804: Bricks Broken Access Control via query_result Endpoint


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-hr55-whqv-38v8

## What is CVE-2026-118804?

CVE-2026-118804 is a high-severity vulnerability in Bricks Builder, published on 28 Oct 2026. 

### Official description

Bricks Builder 2.4.3 and before contains a broken access control vulnerability that allows unauthenticated attackers to access restricted post content by submitting crafted post_status and post_type values in the originalQueryVars parameter to the POST /wp-json/bricks/v1/query_result REST endpoint using a publicly obtainable nonce. Attackers can set post_status to draft or private, or post_type to shop_coupon, to disclose unpublished posts, private content, and WooCommerce coupon data that is otherwise blocked by the standard WordPress REST API routes.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-118804 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118804 is a high-severity vulnerability in Bricks Builder, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118804 in the wild and no public exploit code.

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

## Sources

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

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