CVE-2026-85097
CriticalExploitedBricksforge <= 3.1.8.9 - Unauthenticated Arbitrary File Upload via 'temporaryFileUploads' Parameter
Published Oct 8, 2026 · Updated Oct 8, 2026 · Also known as EUVD-2026-94793, GHSA-jfvp-gc8p-45gp, e993c929-f175-43a7-92e6-9d3b089b8dde
Key Facts
Patch immediately- CVE-2026-85097 is a critical-severity vulnerability (CVSS 9.8 v3.1) affecting Bricksforge (wordpress-plugin).
- It is exploited in the wild, listed in Industry KEV feed, CIRCL KEV since Oct 7, 2026. No public exploit code is known.
- EPSS estimates a 0.3% probability of exploitation in the next 30 days.
- Fixed versions are available, including Bricksforge 3.1.8.10.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
0.3%
Higher than 22.5% of all scored CVEs
Exploited in the wild
Yes
2 catalog listings
Public exploit code
None known
Get the full CVE-2026-85097 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
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.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| Industry KEV feed | Oct 7, 2026 | n/a | Not reported |
| CIRCL KEV | Oct 12, 2026 | n/a | Not reported |
Required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Affected Products
3 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| Bricksforgewordpress-plugin | See advisory | 3.1.8.10 |
Patched Releases
Bricksforge
3.1.8.10
Timeline
Added to Industry KEV feed
Oct 7, 2026
Publicly disclosed
Oct 8, 2026
Added to CIRCL KEV
Oct 12, 2026
Weakness Type
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
- advisoryhttps://www.wordfence.com/threat-intel/vulnerabilities/id/e993c929-f175-43a7-92e6-9d3b089b8dde?source=api-prod
- advisoryhttps://www.wordfence.com/threat-intel/vulnerabilities/id/e993c929-f175-43a7-92e6-9d3b089b8dde?source=api-scan
- exploitVulnCheck exploitation report
- exploitVulnCheck exploitation report
- otherhttps://bricksforge.io/version-changelog/
FAQ
Common Questions.
The Bricksforge plugin for WordPress is vulnerable to unauthenticated arbitrary file upload in versions up to, and including, 3.1.8.9.
Affected: Bricksforge (wordpress-plugin). The full list is in the CVE brief.
It is exploited in the wild, listed in Industry KEV feed, CIRCL KEV since Oct 7, 2026.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including Bricksforge 3.1.8.10.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2026-85097 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo