Skip to content
WP Hack FixEst. 2005

Security news

Bricksforge: a 10-out-of-10 flaw, and attackers are already using it

Published · Disclosed October 8, 2026 · By Adam Taylor

PluginVulnerableFixed in
Bricksforge<= 3.1.8.93.1.8.10 / 4.0.0

If you built your site with Bricks and added Bricksforge for its extra features, check your version today. This flaw scores 10.0 out of 10, the maximum, and it’s already being used in attacks.

Am I affected?

You’re affected if your site runs Bricksforge 3.1.8.9 or earlier. Bricksforge is a paid add-on, so it may not update itself the way free plugins do. Check the version under Plugins in your dashboard.

There are two fixed lines, which has confused some people:

  • 3.1.8.10 fixes this flaw for sites staying on the older 3.x line.
  • 4.0.0 (released September 17) already included the fix, and 4.0.1 fixes a second, separate problem in Bricksforge’s forms that the developer hasn’t described in detail yet.

Our advice: update to the newest 4.x release, 4.0.1 or later. It covers both.

What an attacker can do

Bricksforge’s forms let visitors attach files. The plugin checked what kind of file was being uploaded, but not where it was being sent, so an attacker could disguise a PHP file as an image and have it saved on your server. Once it’s there, they open it and it runs.

No account is needed, and nobody on your side has to click anything. Running their own code on your server means an attacker can do anything the site itself can: add admin accounts, plant backdoors, redirect visitors, or read your database.

Is anyone actually using it?

Yes. Patchstack saw the first attacks on October 7, coming from more than 60 different addresses. The pattern is automated: scripts trying the same upload against site after site, then cycling through variations to get past filters.

What to do

  1. Update Bricksforge to 4.0.1 or later today. If you can’t update right away, deactivate Bricksforge until you can. Your site will lose its Bricksforge features for a while, which is better than the alternative.
  2. Check for files that shouldn’t be there. Using your host’s file manager or FTP, look in wp-content/uploads/bricksforge/tmp/. That folder should hold temporary uploads, never .php files. Anything named like login_admin_something.php is a strong sign you’ve been hit.
  3. Check your users list for administrator accounts you don’t recognise.
  4. If you find anything, don’t stop at deleting it. The file you found is usually the first one, not the only one. Updating closes the hole, but it doesn’t remove anything planted before you did. Get the site checked properly.

On a Protect plan? Plugin updates are part of what we do, so this one is covered.

Worried your site's already been hit?

If something looks wrong, we'll check it and clean it up. If we can't fix it, you don't pay.

We reply within 1 business day (Mon–Fri, 9–5 ET)