CVE-2026-85097

validatedZero produced an exploit or a check.

GHSA-jfvp-gc8p-45gp ↗EUVD-2026-94793 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+1.9dkevAttacks confirmed in the real world.−1d
Bricksforge <= 3.1.8.9
CWE-434 Unrestricted Upload of File with Dangerous Type
ETK-2026-948, permanent identifier
+3.2dTTV
27mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
kev−1.0dtrigger signal (cve.org) +0dpublic poc+1.9dcheck available+3.2dagent stopped
0
+1d
+3d

description

Bricksforge for WordPress through version 3.1.8.9 does not adequately validate a user-supplied file reference during form handling. A remote unauthenticated attacker can upload a server-executable file and run PHP code if they can access the plugin's public form-upload workflow.

mitigation

Disable Bricksforge or its form-upload functionality until the vendor provides an update, and restrict public access to the associated upload workflow where feasible. Configure the web server to prohibit PHP execution in WordPress upload and temporary-file directories.

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.31%22nd percentile
agent run time
27m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-08 06:42Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+1.9d
Δ to kevAttacks confirmed in the real world.
−1d

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-07 00:00Z
  2. 2026-10-08 06:42Z
    cve_org: trigger signal, started the run
  3. 2026-10-10 22:45Z
  4. 2026-10-12 09:02Z
    Attackers Exploit CVSS 10.0 Bricksforge WordPress Flaw Enabling Unauthenticated RCE

this entry in the feed

GET /api/v1/feed/CVE-2026-85097

{
  "etk_id": "ETK-2026-948",
  "cve_id": "CVE-2026-85097",
  "display_id": "CVE-2026-85097",
  "ghsa_id": "GHSA-jfvp-gc8p-45gp",
  "euvd_id": "EUVD-2026-94793",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated arbitrary file upload in Bricksforge for WordPress",
  "summary": "Bricksforge for WordPress through version 3.1.8.9 does not adequately validate a user-supplied file reference during form handling. A remote unauthenticated attacker can upload a server-executable file and run PHP code if they can access the plugin's public form-upload workflow.",
  "mitigation": "Disable Bricksforge or its form-upload functionality until the vendor provides an update, and restrict public access to the associated upload workflow where feasible. Configure the web server to prohibit PHP execution in WordPress upload and temporary-file directories.",
  "vendor": "Bricksforge",
  "product": "Bricksforge",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.1.8.9"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Bricksforge",
      "purl": null
    }
  ],
  "cwes": [
    434
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0031,
  "epss_percentile": 0.2278,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 26.652628233333335,
  "t0_at": "2026-10-08T06:42:09.676000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-11T12:36:22.805418+00:00",
      "days": 3.245985294189815,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T06:42:09.676000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-10-07T00:00:00+00:00",
      "days": -1,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T06:42:09.676000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-85097"
    },
    "public_poc": {
      "at": "2026-10-10T04:51:32+00:00",
      "days": 1.9231750462962962,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T06:42:09.676000+00:00",
      "url": "https://github.com/Wayang1337/CVE-2026-85097"
    },
    "trigger_signal": {
      "at": "2026-10-08T06:42:09.676000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T06:42:09.676000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-85097"
    }
  }
}

published 2026-10-08 07:17Z
last change 2026-10-21 22:34Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.