Bricks Builder 2.4.3 and before contains a broken access control vulnerability that allows unauthenticated attackers
Affects bricks-builderSource GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 29 Oct 2026, 01:13 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Packagistbricks/bricks-builderpkg:composer/bricks/bricks-builderOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, restrict access to the affected REST endpoint if possible or monitor for updates from the vendor.
Description
Bricks Builder versions 2.4.3 and earlier have a broken access control vulnerability that allows unauthenticated attackers to access restricted post content. By submitting crafted post_status and post_type values to a specific REST endpoint with a publicly obtainable nonce, attackers can view unpublished posts, private content, and WooCommerce coupon data that should be restricted.