CVE-2026-118804

waiting for further signalsZero needs more public information before it can validate it.

GHSA-hr55-whqv-38v8 ↗EUVD-2026-112503 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Bricks Builder < 2.4.4
fixed in 2.4.4
ETK-2026-2926Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 47msince last run
1h 10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h40m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Bricks Builder versions 2.4.3 and earlier do not properly enforce access restrictions in a REST query endpoint. An unauthenticated attacker may retrieve unpublished or private WordPress content, including WooCommerce coupon data, when they can obtain a publicly available nonce.

mitigation

Upgrade Bricks Builder to a release newer than 2.4.3 after confirming it includes the vendor's correction. Until upgraded, restrict public access to the affected REST query endpoint at the proxy or WAF where feasible.

fixed in 2.4.4

check
no
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.
–
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.
–
agent run time
1h 10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-28 21:18Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-28 21:18Z
    ghsa: trigger signal, started the run
  2. 2026-10-28 21:18Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2926",
  "cve_id": "CVE-2026-118804",
  "display_id": "CVE-2026-118804",
  "ghsa_id": "GHSA-hr55-whqv-38v8",
  "euvd_id": "EUVD-2026-112503",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper access control in Bricks Builder query endpoint",
  "summary": "Bricks Builder versions 2.4.3 and earlier do not properly enforce access restrictions in a REST query endpoint. An unauthenticated attacker may retrieve unpublished or private WordPress content, including WooCommerce coupon data, when they can obtain a publicly available nonce.",
  "mitigation": "Upgrade Bricks Builder to a release newer than 2.4.3 after confirming it includes the vendor's correction. Until upgraded, restrict public access to the affected REST query endpoint at the proxy or WAF where feasible.",
  "vendor": "Bricks",
  "product": "Bricks Builder",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.4.4"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.4.4"
      ],
      "package_name": "Bricks Builder",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 69.77936225,
  "t0_at": "2026-10-28T21:18:28.475000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-28T21:18:28.475000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T21:18:28.475000+00:00",
      "url": "https://github.com/advisories/GHSA-hr55-whqv-38v8"
    }
  }
}

published 2026-10-29 00:48Z
last change 2026-10-29 05:27Z

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.