Live › vulnerability › CVE-2026-118804
Go to dashboardBricks Builder 2.4.3 and earlier lets an unauthenticated visitor POST crafted post_status and post_type values to its query_result REST endpoint, using a publicly obtainable nonce. An attacker can read draft and private posts and WooCommerce shop_coupon data that standard WordPress REST routes would block.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 22:35 UTC. All times on this page are UTC.
Sites running Bricks Builder 2.4.3 or earlier that expose the Bricks REST query endpoint are exposed, and the risk is greatest where drafts, private posts or WooCommerce coupons exist. Sites without Bricks, or on a newer version, can skip it.
No product ranges from the sources yet.
2.4.3 and earlier are affected./wp-json/bricks/v1/query_result is reachable on the site.2.4.3; the fixed version is unknown from the sources./wp-json/bricks/v1/query_result at the web server or WAF.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Bricks Builder 2.4.3 and before contains a broken access control vulnerability that allows unauthenticated attackers to access restricted post content by submitting crafted post_status and post_type values in the originalQueryVars parameter to the POST /wp-json/bricks/v1/query_result REST endpoint using a publicly obtainable nonce. Attackers can set post_status to draft or private, or post_type to shop_coupon, to disclose unpublished posts, private content, and WooCommerce coupon data that is otherwise blocked by the standard WordPress REST API routes.
This page as .md · .json · in your agent: get_signal("CVE-2026-118804")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.