CVE-2026-85097
CriticalCVSS 9.8Summary
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.
Risk Assessment
An attacker could execute arbitrary PHP code on the server, potentially leading to full compromise of the WordPress site, data theft, or further attacks on the infrastructure.
Recommendation
Update the Bricksforge plugin to the latest version that fixes this vulnerability. Additionally, restrict file upload capabilities and enforce strict file type validation.
Other vulnerabilities in Bricksforge
See all- CVE-2026-34888High
Versions of Bricksforge <= 3.1.8.4 have a vulnerability that allows unauthorized access to sensitive data.
- CVE-2026-84814Critical
Subscriber privilege escalation vulnerability in Bricksforge versions up to 3.1.8.8, allowing a subscriber to escalate privileges.
- CVE-2026-14956Critical
The Bricksforge plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.1.8.6. This is due to improper validation of the fieldIds parameter in the Pro Forms registration action, which allows attacker-supplied field IDs to be added to the trusted form-field whitelist. This makes it possible for unauthenticated attackers to register a new administrator account by submitting a crafted request to a publicly accessible Bricksforge Pro Forms registration form.
- CVE-2026-18030High
The BricksForge WordPress plugin before version 3.1.8.8 does not verify the identity of the requester when processing a password change submitted through one of its form actions. This allows unauthenticated attackers to set an arbitrary password for any user, including administrators, and take over their account. Exploitation requires the site to have a form using the password reset action in update mode; the server-side current-password verification is disabled by default, so the vulnerable state is the default once the action is used.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS