# CVE-2026-85097: Bricksforge <= 3.1.8.9 - Unauthenticated Arbitrary File Upload via 'temporaryFileUploads' Parameter

> Unauthenticated attackers can upload and execute arbitrary PHP code via a crafted file upload parameter in the Bricksforge WordPress plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-jfvp-gc8p-45gp

## What is CVE-2026-85097?

CVE-2026-85097 is a critical vulnerability in Bricksforge, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Bricksforge plugin for WordPress is vulnerable to unauthenticated arbitrary file upload in versions up to, and including, 3.1.8.9. This is due to insufficient validation of the attacker-controlled URL field in the 'temporaryFileUploads' parameter during form submission. An unauthenticated attacker can first obtain a valid nonce via the bricksforge_regenerate_nonce AJAX endpoint, then upload a GIF/PHP polyglot file to the temporary upload directory where MIME type validation is correctly performed. Subsequently, the attacker can submit a form with a crafted 'temporaryFileUploads' parameter where the server-side file path points to the validated GIF file, but the attacker-controlled url field ends with a .php extension. This makes it possible for unauthenticated attackers to upload and execute arbitrary PHP code on the server.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-85097 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85097 exists.

Public exploit code:

- CVE-2026-85097 – Bricksforge WordPress Plugin Unauth File Upload to RCE Toolkit (CVSS 10.0) | Red/Blue Team suite for Bricksforge Pro Forms < 3.1.8.9. 2 tools: Full Exploit (polyglot upload, web shell, mass scan, OPSEC, SQLite/JSON output) + SafeChecker (version detect, non-intrusive audit). Ethical & educational use only. (github_poc): https://github.com/tc4dy/CVE-2026-85097-Toolkit
-  Bricksforge <= 3.1.8.9 Unauthenticated Arbitrary File Upload (github_poc): https://github.com/Wayang1337/CVE-2026-85097
- POC CVE-2026-85097 (github_poc): https://github.com/Masriyan/CVE-2026-85097
- CVE-2026-85097 — Bricksforge <= 3.1.8.9 unauth file upload to RCE. GIF/PHP polyglot + temporaryFileUploads.url mismatch. python3 exploit.py --url http://TARGET (github_poc): https://github.com/BlackHatExploitation/CVE-2026-85097
- For WordPress  (github_poc): https://github.com/RootMantap/CVE-2026-85097
- Bricksforge WordPress Plugin <=3.1.8.9 - Unauthenticated Arbitrary File Upload (nuclei): http/cves/2026/CVE-2026-85097.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85097 is a critical vulnerability in Bricksforge, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85097 exists.

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

## Sources

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

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