Threat reportVulnerabilityTL-2026-3341
Active Exploitation of Bricksforge WordPress Plugin Unauthenticated File Upload / RCE (CVE-2026-85097, CVSS 9.8–10.0)
CVE-2026-85097 in the Bricksforge WordPress plugin (<= 3.1.8.9) lets unauthenticated attackers upload GIF/PHP polyglot files and have them written to a .php path, resulting in remote code execution. Exploitation was first observed on 2026-10-07 at 21:47 UTC from 63 unique source IPs; fixed in 3.1.8.10 (and 4.0.1).
Key facts
| Identifiers | TL-2026-3341, CVE-2026-85097 |
|---|---|
| Severity | CRITICAL |
| CVSS | 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) |
| First disclosed | |
| EPSS | CVE-2026-85097: 0.3% (22.1th percentile) |
| Affected products | Bricksforge Bricksforge WordPress plugin (Pro Forms module) |
| Weaknesses (CWE) | CWE-434 |
| Malware | PHP |
| MITRE ATT&CK techniques | T1027 Obfuscated Files or Information, T1036.008 Masquerading: Masquerade File Type, T1059 Command and Scripting Interpreter, T1136.001 Create Account: Local Account, T1190 Exploit Public-Facing Application, T1505.003 Server Software Component: Web Shell, T1595.002 Active Scanning: Vulnerability Scanning |
| Motivation | UNKNOWN |
| Target sectors | technology, retail, news - media, small-business |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 8 cited sources |
Detection coverage
As of 2026-10-12, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-3341 across Splunk SPL, Microsoft KQL and Sigma, covering 14 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: Bricksforge CVE-2026-85097 Unauthenticated Upload Exploit (temporaryFileUploads PHP URL) - Exploitation [SPL]
Detects exploitation of CVE-2026-85097 in the Bricksforge Pro Forms module: a form_submit request (/wp-json/bricksforge/v1/form_submit or admin-ajax.php action=bricksforge_form_submit) whose temporaryFileUploads parameter pairs an image file path with a url ending in a PHP extension variant (.php, .php5, .phtml, .pht, .phps, %2ephp, .%70hp, .%2570%2568%2570). This is the GIF/PHP polyglot extension-mismatch that yields unauthenticated remote code execution on Bricksforge <= 3.1.8.9.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1190, T1036.008, T1027
- Data sources: stream:http, modsec_audit, waf:json
- Severity: critical
- Confidence: high
Splunk SPL
index=web (sourcetype="stream:http" OR sourcetype="modsec_audit" OR sourcetype="waf:json") "temporaryFileUploads" ("form_submit" OR "bricksforge_form_submit") earliest=-24h@h
| regex _raw="(?i)temporaryFileUploads.{0,600}?(\\.(php[0-9]?|phtml|pht|phtm|phps)|%2ephp|\\.%70hp|\\.%2570%2568%2570)"
| eval src=coalesce(src_ip, src, clientip), dst=coalesce(dest_host, dest_ip, dest, host), request_uri=coalesce(uri_path, uri, url)
| eval encoded_ext=if(match(_raw,"(?i)%2ephp|\\.%70hp|\\.%2570%2568%2570"),"yes","no"), image_file_path=if(match(_raw,"(?i)temporaryFileUploads.{0,600}?\\.(gif|png|jpe?g)"),"yes","no")
| stats count min(_time) as first_seen max(_time) as last_seen values(request_uri) as request_uri values(encoded_ext) as encoded_ext values(image_file_path) as image_file_path by src, dst, sourcetype
| convert ctime(first_seen) ctime(last_seen)Microsoft KQL
CommonSecurityLog
| where TimeGenerated > ago(24h)
| where RequestMethod =~ "POST"
| where RequestURL contains "form_submit" and RequestURL contains "bricksforge"
| extend Body = strcat(tostring(AdditionalExtensions), " ", tostring(Message))
| where Body contains "temporaryFileUploads"
| where Body matches regex @"(?i)temporaryFileUploads.{0,600}?(\.(php[0-9]?|phtml|pht|phtm|phps)|%2ephp|\.%70hp|\.%2570%2568%2570)"
| extend EncodedExtension = Body matches regex @"(?i)%2ephp|\.%70hp|\.%2570%2568%2570"
| extend ImageFilePath = Body matches regex @"(?i)temporaryFileUploads.{0,600}?\.(gif|png|jpe?g)"
| project TimeGenerated, DeviceVendor, DeviceProduct, SourceIP, DestinationIP, RequestURL, RequestMethod, DeviceAction, EncodedExtension, ImageFilePath, BodyExcerpt = substring(Body, 0, 500)Sigma
title: Bricksforge Pro Forms Unauthenticated Upload Exploit - temporaryFileUploads with PHP URL (CVE-2026-85097)
id: 3f1c9a52-7d4e-4b8a-9c21-5e6a0b7d1f34
status: experimental
description: Detects a POST to the Bricksforge form_submit REST route or the bricksforge_form_submit AJAX action carrying a temporaryFileUploads parameter whose url ends in a PHP extension variant (.php, .php5, .phtml, .pht, .phps or URL/double-encoded forms), the GIF/PHP polyglot extension mismatch used to exploit CVE-2026-85097.
references:
- https://patchstack.com/articles/critical-unauthenticated-arbitrary-file-upload-vulnerability-exploited-in-bricksforge-plugin/
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e993c929-f175-43a7-92e6-9d3b089b8dde
- https://app.opencve.io/cve/CVE-2026-85097
author: Threadlinqs Team
date: 2026-10-12
tags:
- attack.initial-access
- attack.t1190
- attack.defense-evasion
- attack.t1036.008
- attack.t1027
- cve.2026-85097
logsource:
category: webserver
detection:
selection_route:
cs-method: 'POST'
cs-uri-stem|endswith: '/bricksforge/v1/form_submit'
selection_ajax:
cs-method: 'POST'
cs-uri-query|contains: 'action=bricksforge_form_submit'
selection_body:
request-body|contains: 'temporaryFileUploads'
selection_php_url:
request-body|re: '(?i)temporaryFileUploads.{0,600}?(\.(php[0-9]?|phtml|pht|phtm|phps)|%2ephp|\.%70hp|\.%2570%2568%2570)'
condition: (selection_route or selection_ajax) and selection_body and selection_php_url
falsepositives:
- Security scanners or penetration tests replaying the public CVE-2026-85097 proof of concept
- Legitimate form submissions never carry a PHP extension in the temporaryFileUploads url value
level: high
Known false positives:
- Security scanners or penetration tests replaying the public CVE-2026-85097 proof of concept
- Custom WAF or logging rules that capture the body of unrelated plugins that also use a temporaryFileUploads parameter
Tuning notes: Requires request-body visibility (WAF, ModSecurity audit log or stream:http); access logs alone do not carry the POST body. Allowlist authorised scanner IPs. Keep the rule after patching to 3.1.8.10 or 4.0.1 for hunting, since attempts continue. Adjust the 600-character window if your WAF truncates bodies.
- Bricksforge CVE-2026-85097 Unauthenticated Upload Exploit (temporaryFileUploads PHP URL) - Exploitation [KQL] · unlock with TL Creds
- PHP Web Shell Staged or Executed Under WordPress Uploads ([indicator], bricksforge/tmp) - Post-Exploitation [KQL] · unlock with TL Creds
- Bricksforge Exploitation Chain, Known Source IPs and Rogue Administrator Creation - Recon/Persistence Correlation [KQL] · unlock with TL Creds
- Bricksforge CVE-2026-85097 Unauthenticated Upload Exploit (temporaryFileUploads PHP URL) - Exploitation [Sigma] · unlock with TL Creds
- PHP Web Shell Staged or Executed Under WordPress Uploads ([indicator], bricksforge/tmp) - Post-Exploitation [Sigma] · unlock with TL Creds
- Bricksforge Exploitation Chain, Known Source IPs and Rogue Administrator Creation - Recon/Persistence Correlation [Sigma] · unlock with TL Creds
- PHP Web Shell Staged or Executed Under WordPress Uploads ([indicator], bricksforge/tmp) - Post-Exploitation [SPL] · unlock with TL Creds
- Bricksforge Exploitation Chain, Known Source IPs and Rogue Administrator Creation - Recon/Persistence Correlation [SPL] · unlock with TL Creds
Indicators of compromise
As of 2026-10-12, Threadlinqs Intelligence tracks 14 indicators of compromise for TL-2026-3341.
Sample indicators (3 of 14)
- IP address:
177.75.57[.]20 - IP address:
23.97.62[.]146 - IP address:
84.247.60[.]125
Defanged, TLP:CLEAR. Full set of 14 indicators: unlock with TL Creds.
Technical analysis
The Bricksforge plugin's Pro Forms module validates MIME type correctly when a file is first uploaded to its temporary directory, but at form submission it trusts client-supplied metadata and does not validate the 'url' field inside the 'temporaryFileUploads' parameter. An unauthenticated attacker first obtains a valid nonce from the unauthenticated 'bricksforge_regenerate_nonce' AJAX endpoint, then uploads a GIF/PHP polyglot (a valid image carrying PHP code) to /wp-content/uploads/bricksforge/tmp/. The attacker then submits the form (POST /wp-json/bricksforge/v1/form_submit, or /wp-admin/admin-ajax.php with action=bricksforge_form_submit) with a 'temporaryFileUploads' entry whose server-side 'file' path points at the validated .gif while the attacker-controlled 'url' ends in .php. The plugin places the file contents at the .php location, and requesting that file executes the embedded PHP. Per the vendor changelog, all sites with Pro Forms active are affected, including those without any upload field.
Patchstack first observed exploitation on 2026-10-07 at 21:47:17 UTC, from 63 unique source IPs. Six IPs (a mix of ISP, datacenter and cloud-provider address space) produced about 46% of requests, consistent with automated exploitation over rotating proxies. Two clusters were described: 44 IPs sending 56 requests with identical payloads within seconds, and 3 IPs cycling through 25 PHP extension and encoding variations (.php5, .php7, .php8, .phtml, .pht, .phtm, .phps, mixed case, and URL-encoded forms such as %2ephp, .%70hp, .%2570%2568%2570) against the same file, also altering the path, name, originalFilename and url metadata fields. About 95% of captured requests disguised the payload as GIF/PNG. Post-exploitation indicators reported by Patchstack include unexpected PHP files in the Bricksforge tmp directory or the uploads tree, files named login_admin_*.php under /wp-content/uploads/YYYY/MM/, and unauthorized administrator accounts. The sources name no threat actor and no malware family; no second-stage payload was documented for this vulnerability.
Scoring differs by source: Wordfence/OpenCVE record CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-434), while Patchstack and The Hacker News cite 10.0. The 9.8 vector is recorded here because it is the only published vector. Patchstack tracks roughly 6,000 active installations. Dr. Web (drweb.de) notes this is the third critical Bricksforge vulnerability in five weeks, following CVE-2026-84814 (CVSS 9.8, subscriber-to-administrator privilege escalation, disclosed Sept 2, fixed in 3.1.8.9) and CVE-2026-18030 (CVSS 8.1, unauthenticated password reset via Pro Forms, disclosed Sept 18, fixed in 3.1.8.8). Bricksforge versions up to and including 3.1.8.9 are vulnerable; 3.1.8.10 fixes it and 4.0.1 (released 2026-10-08) is the recommended release. Patchstack offers a RapidMitigate virtual patch as interim protection. Defenders should treat any site that ran a vulnerable version since 2026-10-07 as potentially compromised.
MITRE ATT&CK techniques by tactic:
Defense Evasion
T1027 Obfuscated Files or Information; T1036.008 Masquerading: Masquerade File Type
Execution
T1059 Command and Scripting Interpreter
Persistence
T1136.001 Create Account: Local Account; T1505.003 Server Software Component: Web Shell
Initial Access
T1190 Exploit Public-Facing Application
Reconnaissance
Remediation
Patches
- Bricksforge 3.1.8.10
- Bricksforge 4.0.1 (released 2026-10-08)
Immediate actions
- Update Bricksforge to 3.1.8.10 or later (4.0.1 recommended); if patching is not possible, deactivate and remove the plugin
- Search /wp-content/uploads/bricksforge/tmp/ and the wp-content/uploads/YYYY/MM/ tree for unexpected .php/.php5/.php7/.phtml/.pht/.phps files and login_admin_*.php files
- Audit WordPress administrator accounts for unauthorized users and rotate credentials and salts on any site where exploitation is suspected
- Review web access logs from 2026-10-07 onward for requests to /wp-json/bricksforge/v1/form_submit and admin-ajax.php?action=bricksforge_form_submit containing temporaryFileUploads
Workarounds
- Apply Patchstack RapidMitigate rule for traffic-layer blocking
- Block or restrict unauthenticated access to the bricksforge_regenerate_nonce and bricksforge_form_submit endpoints until patched
Longer-term hardening
- Block PHP execution in wp-content/uploads at the web server level
- Deploy a WAF or virtual patching that inspects temporaryFileUploads parameters for image-path/.php-URL mismatches
- Run file integrity monitoring on WordPress web roots and alert on new PHP files in upload directories
Affected and fixed versions
- Bricksforge — Bricksforge WordPress plugin (Pro Forms module)
Vulnerable versions: <= 3.1.8.9
Fixed in: 3.1.8.10; 4.0.1
Timeline
- Bricksforge 3.1.8.9 is released with email-template security hardening; this is the last version vulnerable to CVE-2026-85097.
- CVE-2026-84814 (CVSS 9.8, subscriber-to-administrator privilege escalation) is disclosed in Bricksforge, the first of three critical flaws in five weeks.
- Bricksforge 4.0.0 is released as a major redesign of the plugin.
- CVE-2026-18030 (CVSS 8.1, unauthenticated password reset via Pro Forms) is disclosed in Bricksforge.
- Exploitation continues from 63 unique source IPs, including a cluster of 44 IPs sending identical payloads and 3 IPs testing 25 PHP extension/encoding variations.
- Patchstack first observes in-the-wild exploitation of the Bricksforge file upload flaw at 21:47:17 UTC.
- Bricksforge 4.0.1 is released with a Pro Forms file upload security fix; 3.1.8.10 also contains the fix.
- CVE-2026-85097 is published (CVSS 3.1 9.8, CWE-434) for Bricksforge versions through 3.1.8.9.
- The Hacker News publishes reporting on active exploitation of the Bricksforge flaw, citing Patchstack and Wordfence.
Sources cited
- Patchstack: Critical unauthenticated arbitrary file upload vulnerability exploited in Bricksforge plugin patchstack.com · Advisory
- OpenCVE: CVE-2026-85097 app.opencve.io · Advisory · 2026-10-08
- INCIBE-CERT: CVE-2026-85097 incibe.es · Advisory
- Wordfence Threat Intel: Bricksforge vulnerability e993c929-f175-43a7-92e6-9d3b089b8dde wordfence.com · Research
- Bricksforge version changelog bricksforge.io · Vendor report · 2026-10-08
- Attackers Exploit CVSS 10.0 Bricksforge WordPress Flaw Enabling Unauthenticated RCE The Hacker News · News · 2026-10-12
- Dr. Web: Bricksforge Sicherheitslücke Upload aktiv ausgenutzt drweb.de · News
- TheHackerWire: CVE-2026-85097 thehackerwire.com · News
Previous and next in vulnerability
Drafted by the Threadlinqs research pipeline from 8 sources; published ; last updated —.