# CVE-2026-118803: Bricks Theme Unauthenticated Dynamic Data Tag Injection via query_result


- **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-33cw-hwxh-f8g5

## What is CVE-2026-118803?

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

### Official description

Bricks Theme 2.4.3 and before contains an unauthenticated dynamic-data tag injection vulnerability that allows anonymous attackers to control the urlParams object in the query_result REST endpoint, causing the submitted value to be re-parsed as a Bricks dynamic data tag. Attackers can inject tags such as author_meta:user_pass, author_meta:user_email, or cf_coupon_amount to leak post meta and the post author's user record, including the password hash, without authentication.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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


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

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

## Is CVE-2026-118803 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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