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

Published Oct 8, 2026
·
Updated

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 bricksforgeregeneratenonce 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.

Affected Software

1 affected component
Bricksforge BricksForge WordPress plugin<=3.1.8.9

Event History

Oct 8, 2026
CVE Published
via MITRE·06:42 AM
Data Sourced
via MITRE·06:42 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What does an attacker need to exploit this issue?

The attacker does not need authentication or user interaction. They can obtain a valid nonce from the bricksforge_regenerate_nonce AJAX endpoint, upload a GIF/PHP polyglot to the temporary upload directory, and then submit a crafted temporaryFileUploads parameter that causes the file to be treated as a PHP file.

2

Which installations are affected?

Bricksforge for WordPress versions up to and including 3.1.8.9 are affected. The provided data does not identify any configuration prerequisite beyond the vulnerable plugin being present.

3

What is the likely impact of successful exploitation?

Successful exploitation allows an unauthenticated attacker to upload and execute arbitrary PHP code on the server. This can result in full compromise of the confidentiality, integrity, and availability of the affected WordPress environment.

4

How can I determine whether exploitation may have occurred?

Review the temporary upload directory for unexpected files, especially files involving GIF/PHP polyglots or files with PHP extensions. Also review form submissions and requests involving the temporaryFileUploads parameter and the bricksforge_regenerate_nonce AJAX endpoint.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203