ZeroBreach Request early access
← All Attack Surface
critical CVE-2026-85097

Bricksforge 3.1.8.9 and earlier allows unauthenticated file upload to RCE, under active exploit (CVE-2026-85097)

Tags: wordpress, php, plugin, bricksforge, file-upload, exploited

Bricksforge, a commercial add-on for the Bricks visual site builder, ships a critical flaw (CVE-2026-85097, CVSS 9.8) in versions 3.1.8.9 and earlier. The plugin performs no capability checks on file uploads, so an unauthenticated attacker can upload an arbitrary file and execute malicious code on the site.

WordPress security firm Patchstack began seeing in-the-wild exploitation attempts on October 7, 2026. Its telemetry shows automated campaigns running over rotating proxies: one cluster of 44 IPs sent 56 identical payload requests within seconds of each other, while another tested 25 PHP extension and encoding variations against the same temporary file. Patchstack reports roughly 6,000 websites run Bricksforge.

A successful attack hands the intruder full control of the site: webshells, stolen data, and a foothold for further malware. The vendor patched the flaw in version 3.1.8.10.

What to do

  • Update Bricksforge to 3.1.8.10 immediately, or remove it if you cannot update.
  • If you were running 3.1.8.9 or earlier, treat the site as potentially compromised. Look for unknown administrator users and rogue PHP files, then rotate credentials and salts.
  • Watch WAF and access logs for the attack patterns Patchstack described: rapid identical payload bursts and PHP extension probing against upload endpoints.

This is exactly the class of flaw ZeroBreach’s recurring scans are built to catch: a critical plugin CVE under active exploit, the fixed version identified, and a post-patch compromise check, on a schedule instead of when you remember. Keeping every plugin inventoried means Bricksforge never hides in the forgotten corner of a site.