Security notice
Use Bricksforge, the paid add-on for the Bricks builder? Someone without a login can upload files that can lead to a site takeover. Update to 3.1.8.10 or later today.
Bricksforge, a premium add-on for the Bricks WordPress builder, has CVE-2026-85097 in versions 3.1.8.9 and earlier. It lets someone without a login upload files to the site, which can lead to a site takeover. Patchstack rates it CVSS 10 (critical) and marks it as known to be exploited. The EU vulnerability database lists a CVSS 3.1 score of 9.8 and names Wordfence as the CVE Numbering Authority. Patchstack published its database entry on October 7, 2026. In an October 8 article, Patchstack said it first observed attacks against this flaw on October 7, 2026. The fix is version 3.1.8.10. Later Bricksforge releases also include this fix. This is a premium add-on, so check that your license is active and the update actually arrived. If you use Bricksforge, update to 3.1.8.10 or later today, preferably the latest version. If you cannot update, deactivate the add-on until you can. (Patchstack, Oct 7, Patchstack article, Oct 8, Bricksforge changelog)
What happened
- The flaw. CVE-2026-85097 affects Bricksforge, a premium add-on for the Bricks WordPress builder, in versions 3.1.8.9 and earlier. Someone without a login can upload files to the affected site. That can lead to a site takeover. (Patchstack, Patchstack article)
- Known to be exploited, per Patchstack. Patchstack marks this vulnerability as known to be exploited. In its October 8, 2026 article, Patchstack said it first observed attacks against this flaw on October 7, 2026. That is Patchstack's own assessment. (Patchstack, Patchstack article)
- Severity. Patchstack rates it CVSS 10 (critical). The EU vulnerability database lists a CVSS 3.1 score of 9.8 and names Wordfence as the CVE Numbering Authority for this record. (Patchstack, EUVD)
- The fix. The first fixed version is 3.1.8.10. Bricksforge's changelog for version 4.0.1, dated October 8, 2026, says CVE-2026-85097 was an arbitrary file upload that was fixed earlier in 3.1.8.10 and in 4.0.0, and it also describes a further security fix in the same area. Later releases, including the current 4.1.0, follow those fixed versions. Update to 3.1.8.10 or later, preferably the latest version. (Patchstack, Bricksforge changelog)
- Advisory date. Patchstack published its database entry on October 7, 2026. The GitHub advisory record was published October 8, 2026. EverThread had no earlier notice for this CVE. (Patchstack, GitHub advisory GHSA-jfvp-gc8p-45gp)
- Install base. Patchstack's article badge lists Bricksforge at about 6,000 sites. That is not a count of sites that are still on a vulnerable version, and it is not a count of sites that have been attacked. (Patchstack article)
Who should worry
Any WordPress site running Bricksforge 3.1.8.9 or earlier. This is a paid add-on for the Bricks builder, not Bricks itself. If you do not use Bricksforge, this notice does not apply to you.
What to do now
- Update Bricksforge to 3.1.8.10 or later today, preferably the latest version. Back up the site first. This is a premium add-on, so confirm your license is active, then in WordPress admin go to Plugins, Installed Plugins, and confirm the installed version even if automatic updates are enabled or your host manages updates. (Patchstack, Bricksforge changelog)
- If the update has to wait, deactivate the add-on until you can install the fixed version.
- Check for signs of tampering. Look for unexpected new files, especially in upload folders, unexpected new administrator or user accounts, changed passwords, and odd settings. Updating closes the flaw; it does not undo access an attacker may already have gained.
- If you find signs of a break-in, change passwords, tell affected users, and ask your developer or host to investigate.
What to send your developer, agency or host
Please check whether our WordPress site runs Bricksforge, a premium add-on for the Bricks builder. CVE-2026-85097 affects versions 3.1.8.9 and earlier; unauthenticated attackers can upload files that can lead to site takeover, fixed in 3.1.8.10. Patchstack rates it 10 and marks it as known to be exploited. Please update us to 3.1.8.10 or later today, preferably the latest version, or deactivate the add-on until the update can be installed, then check for unexpected files, accounts or activity, and confirm the version you left us on. Sources: Patchstack, Patchstack article, Bricksforge changelog, EUVD, NVD.
Common questions
Does this mean my site was hacked?
No. A vulnerable version is a reason to update and review the site, not proof of a break-in. Patchstack marks this flaw as known to be exploited, so do not wait.
Can EverThread tell me if I am affected?
No. EverThread does not test for this. We cannot see which WordPress plugins or add-ons your site runs or which versions they are on. A scan without a warning about this add-on does not mean your site is safe.
Which version should I install?
3.1.8.10 is the first version that fixes this flaw. Install 3.1.8.10 or later, preferably the latest Bricksforge release. You need an active Bricksforge license to receive the update. (Patchstack, Bricksforge changelog)
Why is this notice coming out in November if the advisory is from October?
Patchstack published the advisory on October 7, 2026. EverThread did not have a notice for this CVE before today. The flaw is still worth updating for if you have not already installed 3.1.8.10 or later.
Where can I follow updates?
Follow Patchstack, the Patchstack article, the Bricksforge changelog, the EUVD entry and the NVD entry. All current notices are on our notices page.
Security alerts by email
Hear about the next one first.
When a flaw puts websites at risk, we send one email: what happened, who it affects and what to do. It's free, whether or not you use EverThread.
Sources
- Patchstack database, CVE-2026-85097: published October 7, 2026. Bricksforge versions 3.1.8.9 and earlier. Patched in 3.1.8.10. Rated 10. Required privilege: unauthenticated. Marked known to be exploited.
- Patchstack article, October 8, 2026: unauthenticated file upload, CVSS 10.0, affected versions through 3.1.8.9, fixed in 3.1.8.10. Patchstack said it first observed attacks against this flaw on October 7, 2026, and described Bricksforge as used on about 6,000 sites.
- Bricksforge version changelog: the 4.0.1 entry, dated October 8, 2026, says CVE-2026-85097 was an arbitrary file upload that was fixed earlier in 3.1.8.10 and in 4.0.0, and describes a further security fix in the same area. The 3.1.8.10 changelog entry itself was not in the first page of that history when checked on November 16, 2026.
- EUVD-2026-94793: CVSS 3.1 score 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Names Wordfence as the CVE Numbering Authority. Published October 8, 2026.
- GitHub advisory GHSA-jfvp-gc8p-45gp: published October 8, 2026. Describes CVE-2026-85097 as unauthenticated arbitrary file upload in Bricksforge 3.1.8.9 and earlier.
- NVD CVE-2026-85097: CVE record for this vulnerability.
- WP Server Guard, November 2026 plugin briefing: last reviewed November 16, 2026. Lists Bricksforge CVE-2026-85097, citing Patchstack, versions through 3.1.8.9, fix 3.1.8.10, CVSS 10, published October 7.