Attacks reportedCVE published · 8 Oct 2026
Bricksforge
CVE-2026-85097 Severity · Critical
CVSS 9.8
Affected
Up to and including 3.1.8.9
Fixed in
3.1.8.10 and 4.0.0

CVE alert · WordPress

CVE-2026-85097: Bricksforge lets anyone with no account upload and run PHP code

Anyone on the internet can upload PHP code (the language WordPress runs on) through Bricksforge up to 3.1.8.9 and take over your site. Patchstack has seen attacks since 7 October 2026, so update to 3.1.8.10 or later today.

Check your systems with your AI agent

Paste this prompt into an AI agent that can run commands on your machines. It only reads versions and settings, asks before using administrator rights, and ends with a report.

Check whether my systems are affected by CVE-2026-85097 in Bricksforge, then write me a report.

Read the alert first: https://securityaudit.ae/cve/cve-2026-85097-bricksforge/

What the alert says (facts checked 23 October 2026):
- Affected: Up to and including 3.1.8.9
- Fixed in: 3.1.8.10 and 4.0.0
- Exploited: Yes: Patchstack saw attacks from 7 October 2026; not in CISA's KEV catalog as of 23 October 2026

Rules:
- Read only. Do not install, update, restart, delete or change anything, and never run exploit or proof-of-concept code.
- Run only commands that read versions or settings. Ask me before any command that needs sudo or administrator rights.
- If you do not know which machines, containers, cloud accounts or sites are in scope, ask me for the list before you start.
- If a machine cannot be reached or a command fails, say so. Do not guess.

Steps:
1. Find where Bricksforge runs: servers, containers and their hosts, cloud services, sites.
2. On each one, read the installed version and the settings the alert names. The alert gives these commands:

    wp plugin get bricksforge --field=version

    wp plugin list --fields=name,status,version

3. Compare each version with the affected and fixed versions above. When a vendor or a distribution ships its own fixed package, the alert names it.
4. Report: one line per machine or service with the version found, Affected, Not affected or Unknown, and the evidence (the command and its output). Then the actions to take, in order, from the alert's "How to fix" section, and what you could not check.

Key facts

FactDetail
ProductBricksforge (WordPress plugin for Bricks Builder)
Affected versionsUp to and including 3.1.8.9
Fixed in3.1.8.10 and 4.0.0
Severity9.8 Critical (CVSS 3.1, Wordfence); 10.0 Critical (CVSS 3.1, Patchstack)
Who can attackAnyone on the internet, with no account or login
ExploitedYes: Patchstack saw attacks from 7 October 2026; not in CISA's KEV catalog as of 23 October 2026
CVE published8 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:

shell
wp plugin get bricksforge --field=version

You can also list all plugins and read the bricksforge row:

shell
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

  1. 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).
  2. If you cannot update yet, the sources give no workaround: neither the vendor changelog nor the Wordfence advisory offers one.
  3. 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.php calls and requests to new PHP files under /wp-content/uploads/. In the temporaryFileUploads content, 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:

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

Web app and API security test

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

Ask for a quote Book a call

Sources

  1. CVE-2026-85097 record CVE Program
  2. Bricksforge <= 3.1.8.9 - Unauthenticated Arbitrary File Upload via 'temporaryFileUploads' Parameter Wordfence Intelligence (Defiant)
  3. Critical Unauthenticated Arbitrary File Upload Vulnerability Exploited in Bricksforge Plugin Patchstack
  4. Bricksforge Version History (changelog) Bricksforge
  5. Known Exploited Vulnerabilities Catalog CISA

More CVE alerts

All CVE alerts