Skip to main content

Bricks Builder CVE-2026-118804

| EUVDEUVD-2026-112503 HIGH
Missing Authorization (CWE-862)
2026-10-28 VulnCheck GHSA-hr55-whqv-38v8
7.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain public nonce from site
  2. Exploit
    Send crafted query_result POST request
  3. Execution
    Bypass authorization with draft/private/shop_coupon values
  4. Impact
    Exfiltrate restricted post and coupon data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a WordPress site running the Bricks Builder plugin/theme at version 2.4.3 or earlier with the /wp-json/bricks/v1/query_result REST endpoint reachable (standard in affected installs). The attacker must supply a nonce, which the description states is publicly obtainable, so this is not a practical limiting factor; no user authentication, no privileges, and no user interaction are required. Exploitation is performed by submitting crafted post_status (draft/private) or post_type (shop_coupon) values in the originalQueryVars parameter. The primary limiting factor is simply having a vulnerable Bricks version installed and internet-reachable; there is no indication a non-default configuration is needed.

Impact

This is a credible, near-term priority rather than an inflated high-CVSS score. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) reflects what the description confirms: a remote, low-complexity request to a REST endpoint with no authentication, using a nonce the description explicitly calls 'publicly obtainable,' so the nonce is not a meaningful barrier. Impact is confidentiality-only (C:H/I:N/A:N) - disclosure of unpublished, private, and WooCommerce coupon data - which matches CWE-862 (Missing Authorization). The vuln.today decision label is 'this_week,' and the finding is attributed to VulnCheck with a dedicated advisory, lending analyst credibility. Key signals are MISSING: no EPSS score, no CISA KEV listing, and no confirmed public exploit code are present in the input, so exploitation probability cannot be quantified. There is no conflict between the CVSS vector and the description - both agree on remote unauthenticated access. Net: a real, easily-triggered data-disclosure bug in a popular WordPress builder, worth prioritizing on the vendor's 'this_week' timeline, but with no evidence of active or automated exploitation at the time of analysis.

Exploit ScenarioDerived

An unauthenticated attacker obtains the publicly available nonce from a Bricks-powered WordPress site, then sends a crafted POST to /wp-json/bricks/v1/query_result with originalQueryVars setting post_status to draft/private or post_type to shop_coupon. The endpoint returns content the standard WordPress REST API would block, exposing unpublished posts, private pages, and WooCommerce coupon codes. No public exploit code is identified in the provided data, though the attack is simple enough to reproduce from the advisory description.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 28, 2026

Broken access control in the Bricks Builder WordPress plugin/theme through version 2.4.3 lets unauthenticated remote attackers read content that WordPress would otherwise withhold, including draft and private posts and WooCommerce coupon records, through the plugin's /wp-json/bricks/v1/query_result REST endpoint. An attacker submits crafted post_status and post_type values inside the originalQueryVars parameter; the required nonce is described as publicly obtainable, so it does not act as a real barrier, and no authentication or user interaction is needed. Scored 7.5 with confidentiality-only impact (CWE-862) and flagged as a this-week priority; no public exploit identified at time of analysis.

RemediationAI

Upgrade Bricks Builder to version 2.4.4, the release identified in the vendor's advisory at https://bricksbuilder.io/release/bricks-2-4-4/, which addresses the missing authorization check on the query_result endpoint; the VulnCheck advisory at https://www.vulncheck.com/advisories/bricks-broken-access-control-via-query-result-endpoint provides additional detail. Because the vulnerable route is part of a standard affected installation and the nonce is publicly obtainable, the vendor-supplied update is the complete fix, and no separate vendor-documented workaround is provided in the available references. Inventory WordPress sites for Bricks 2.4.3 and earlier and prioritize those that are internet-reachable, since exploitation requires no credentials and no user interaction.

Affected VersionsENISA

Bricks Builder 0 <2.4.4

Affected Packages

euvd bricks_builder fix: 2.4.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a missing-authorization case (CWE-862) in a WordPress plugin that exposes its own REST route, /wp-json/bricks/v1/query_result, rather than relying solely on core WordPress REST endpoints. Bricks Builder builds a query from caller-supplied originalQueryVars, and because the endpoint does not enforce the capability and visibility checks that the standard WordPress REST API applies, an attacker can set post_status to draft or private, or post_type to shop_coupon, to reach records that core routes would filter out. WordPress nonces are CSRF tokens tied to a session and are not an authorization control; the advisory notes that a usable nonce is publicly obtainable, so possession of one does not restrict who can call the endpoint. The affected package is tracked as CPE cpe:2.3:a:bricks:bricks_builder:*:*:*:*:*:*:*:*, covering releases up to and including 2.4.3.

Know when Bricks gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY HIGH
NVD 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 7.5 HIGH

Remote REST endpoint reachable without authentication via a publicly obtainable nonce (PR:N, AV:N, AC:L, UI:N); impact is restricted-content disclosure only, so C:H with I:N/A:N.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
Patch available
Oct 28, 2026 - 22:04 EUVD
CVE Published
Oct 28, 2026 - 21:18 cve.org
HIGH 7.5

DescriptionNVD

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.

Executive ViewAI

Why It Matters

CVE-2026-118804 is a high-severity broken access control flaw in the Bricks Builder WordPress plugin/theme (up to 2.4.3) that allows unauthenticated attackers to read sensitive content such as draft/private posts and WooCommerce coupon records. This affects all organizations using the vulnerable plugin, potentially exposing confidential business information and customer data, which could lead to reputational damage, regulatory scrutiny, and loss of customer trust.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

Prevalence
Medium
popular premium WordPress site builder, common but not everywhere
Social Media
1
Sightings
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS N/A
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy