Patchstack has confirmed active attacks against a critical Bricksforge vulnerability that can let unauthenticated attackers upload and execute PHP code. The flaw, tracked as CVE-2026-85097, has a CVSS score of 10.0. Bricksforge users should update to version 3.1.8.10 or later now.
Short answer: Bricksforge versions 3.1.8.9 and earlier are affected. Install version 3.1.8.10 or later, then review HTTP and application logs and check upload directories for unexpected PHP files. Patchstack observed the first exploitation attempts on October 7, 2026, at 21:47:17 UTC.
Patchstack’s October 8 security report says the vulnerability needs no authentication and can lead to remote code execution. That makes this an immediate update, not a routine plugin maintenance task.
What the Bricksforge vulnerability affects
The issue affects Bricksforge, a WordPress plugin that extends Bricks Builder with features including forms, animations, custom interactions, and dynamic data tools. Patchstack identifies every release through 3.1.8.9 as affected. Version 3.1.8.10 contains the fix.
The reported weakness is in how Bricksforge handles uploaded file metadata during form submission. It checks a file’s MIME type when the file is first uploaded, but later trusts metadata supplied by the client. Specifically, Patchstack says the plugin does not validate the url field inside the temporaryFileUploads parameter.
An attacker can exploit that mismatch to get a file that passes the initial image check treated as a PHP file at its destination. If the PHP file is then requested, the server can execute the code it contains. Patchstack rates the vulnerability CVSS 10.0, its critical severity rating, and says attackers can exploit it without logging in.
How attacks appear in site logs
Patchstack says nearly all observed attempts targeted Bricksforge’s REST API form-submission endpoint. One other request pattern used the WordPress admin AJAX endpoint with the Bricksforge form-submit action. Requests included a crafted temporaryFileUploads parameter.
The most useful sign to check is a mismatch between the uploaded file path and its destination. For example, an image path ending in .gif or .png paired with a destination URL ending in a PHP-related extension is suspicious. Patchstack says 95% of captured requests used a server-side path ending in .gif or .png, with most of those paired with a PHP-related destination.
Review logs and files for these indicators:
- POST requests to
/wp-json/bricksforge/v1/form_submitcontainingtemporaryFileUploads. - Image file paths paired with destination URLs ending in a PHP-related extension.
- Calls to the
bricksforge_regenerate_nonceaction followed by upload and form-submission activity. - Unexpected PHP files in
/wp-content/uploads/bricksforge/tmp/or other uploads directories. - Files with names matching
login_admin_*.php, or requests to newly created PHP files in uploads.
Patchstack also reported attempts using alternative, mixed-case, and encoded PHP extensions, along with changes to file metadata fields. A search limited to the exact lowercase extension .php may therefore miss some suspicious requests.
What to do if your site runs Bricksforge
Update to the fixed release
Upgrade Bricksforge to version 3.1.8.10 or later. This is the primary fix identified by Patchstack. If you manage multiple WordPress sites, check each installation rather than assuming a shared update schedule covered all of them.
Patchstack says its mitigation rule was in place before the first exploitation attempt it observed. That protection may help block attack traffic for sites covered by the rule, but it does not replace installing the fixed plugin version.
Check for evidence of attempted or successful exploitation
If a site was running an affected version, review historical HTTP and application logs as well as the current file system. Look for suspicious form submissions, the image-to-PHP destination mismatch, and unexpected PHP files in temporary or regular uploads directories. Also check whether anyone requested newly created PHP files in those locations.
These indicators can help identify suspicious activity, but their presence alone does not establish the full scope of an incident. If you find an unexpected executable file or related unauthorized changes, treat the site as potentially compromised and investigate it with your incident-response process. Updating the plugin closes the reported flaw; it does not by itself determine whether an attacker already used it.
FAQ
Which Bricksforge versions are affected?
Patchstack lists versions 3.1.8.9 and earlier as affected by CVE-2026-85097. Version 3.1.8.10 is the fixed release.
Does exploiting the flaw require a WordPress account?
No. Patchstack describes the vulnerability as unauthenticated, so an attacker does not need to log in to exploit it.
What should I check after updating Bricksforge?
Review logs for suspicious form submissions and check upload directories for unexpected PHP files, especially in the Bricksforge temporary upload path. If you find suspicious files or unauthorized changes, investigate the site rather than treating the software update as proof that no compromise occurred.
Next step: Check your Bricksforge version and update to 3.1.8.10 or later today.