Key facts
| Fact | Detail |
|---|---|
| Product | Bricksforge (WordPress plugin for Bricks Builder) |
| Affected versions | Up to and including 3.1.8.9 |
| Fixed in | 3.1.8.10 and 4.0.0 |
| Severity | 9.8 Critical (CVSS 3.1, Wordfence); 10.0 Critical (CVSS 3.1, Patchstack) |
| Who can attack | Anyone on the internet, with no account or login |
| Exploited | Yes: Patchstack saw attacks from 7 October 2026; not in CISA's KEV catalog as of 23 October 2026 |
| CVE published | 8 October 2026 |
What an attacker can do
CVE-2026-85097 lets an attacker upload a file type the plugin should refuse. It leads to remote code execution (the attacker runs their own code on your web server).
The flaw is in Pro Forms, the Bricksforge forms feature. The plugin trusts a url field that the visitor sends inside the temporaryFileUploads form parameter. The attacker first uploads a file that is both a valid GIF image and PHP code, so it passes the image check. Then they submit a form that points to that image with a destination ending in .php. The plugin writes the content to a PHP file, and the server runs it.
Patchstack says this lets an attacker install web shells (hidden pages that control the server), change site content, read sensitive data and keep access. In practice, that is a full takeover of the site. If it stores customer details, assume the attacker can read them.
Who is affected
Every version up to and including 3.1.8.9 is vulnerable. The plugin is an add-on for Bricks Builder.
The attacker needs no account and no action from anyone on your side. They first ask the plugin for a security token through bricksforge_regenerate_nonce, which answers any visitor. They then send the form to /wp-json/bricksforge/v1/form_submit, or to admin-ajax.php with the action bricksforge_form_submit.
The sources do not say whether the site needs a published form with an upload field. Treat any site on a vulnerable version as exposed.
The wordpress.org directory does not list Bricksforge, so there is no official install count. Patchstack's advisory shows a figure of 6K next to a download icon but does not say what it counts. If an agency or freelancer built your site with Bricks Builder, ask them whether the plugin is installed.
How to check your version
If you have WP-CLI (the WordPress command-line tool) on the server, run this in the WordPress folder:
wp plugin get bricksforge --field=version
You can also list all plugins and read the bricksforge row:
wp plugin list --fields=name,status,version
Without command-line access, log in to the WordPress admin. Go to Plugins > Installed Plugins and read the version in the Bricksforge row.
Version 3.1.8.9 or lower is vulnerable.
What to do now
- Update Bricksforge to 3.1.8.10 or later today; that fixes CVE-2026-85097. The vendor also fixed a second upload flaw in Pro Forms. It affects every site using that feature, even with no upload field, and the vendor strongly recommends the update. The changelog lists no 3.x release with that fix, so move to 4.0.1 or later (latest: 4.0.2, 13 October 2026).
- If you cannot update yet, the sources give no workaround: neither the vendor changelog nor the Wordfence advisory offers one.
- Check your web server and application logs, old ones too. A standard access log shows only the URL. Look there for
POST /wp-json/bricksforge/v1/form_submit,admin-ajax.phpcalls and requests to new PHP files under/wp-content/uploads/. In thetemporaryFileUploadscontent, attackers pair an image path with a PHP destination and try one extension after another. That content appears only in logs that record the data sent with each request, such as a web application firewall or security plugin log.
Is it being exploited?
Yes. Patchstack reported active attacks on 8 October 2026. It saw the first one at 21:47:17 UTC on 7 October 2026, the day Wordfence made the flaw public. Attempts came from 63 IP addresses and looked automated. Patchstack says its RapidMitigate rule blocks these requests for its customers.
The flaw is not in the CISA KEV catalog (the US government list of flaws known to be exploited) as of 23 October 2026. The CVE record also carries a Vulnrichment assessment (the agency's risk notes on each flaw), dated 8 October 2026 at 14:24 UTC, which says "Exploitation: none". That note came after Patchstack published its report at 11:28 UTC and has not changed since.
To find uploaded PHP files, run this in the WordPress folder:
find wp-content/uploads -type f -iname "*.ph*"
Check every match, starting with /wp-content/uploads/bricksforge/tmp/ and files named login_admin_*.php. Search your logs for the most active attacking addresses: 177.75.57.20, 23.97.62.146, 84.247.60.125, 38.154.185.97, 150.109.16.166 and 153.75.90.146.
Get help
Updating closes this flaw. Flaws in your own code get no CVE and no update, and a test of your app is how they are found.
A penetration test of your web app and its API: who can see whose data, and what an attacker can change.
From AED 20,000, excl. 5% VAT
Sources
- CVE-2026-85097 record CVE Program
- Bricksforge <= 3.1.8.9 - Unauthenticated Arbitrary File Upload via 'temporaryFileUploads' Parameter Wordfence Intelligence (Defiant)
- Critical Unauthenticated Arbitrary File Upload Vulnerability Exploited in Bricksforge Plugin Patchstack
- Bricksforge Version History (changelog) Bricksforge
- Known Exploited Vulnerabilities Catalog CISA