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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Public exploits 5
- BlackHatExploitation/CVE-2026-85097 PoC on GitHub
- Masriyan/CVE-2026-85097 PoC on GitHub
- RootMantap/CVE-2026-85097 PoC on GitHub
- Wayang1337/CVE-2026-85097 PoC on GitHub
- tc4dy/CVE-2026-85097-Toolkit PoC on GitHub
Each line links to the index that lists it, never to exploit code. Exploit-DB's "verified" and a Metasploit rank of good or better count as verified; a PoC-in-GitHub entry is a repository's claim.
In the news 1
Change history 1
- First seenCVSS 9.8NVD modified 2026-10-08 17:24
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.