Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRequest public nonce via bricks_regenerate_query_nonce
-
ExploitCall load_popup_content REST endpoint
-
ExecutionIncrement popupId to enumerate posts
-
ImpactDisclose unpublished draft content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | No special configuration is required - the load_popup_content REST endpoint is exposed by default in Bricks Theme 2.4 and earlier and performs no status or capability check, so exploitation works against default installations. Prerequisites an attacker must satisfy: obtain a public nonce via the bricks_regenerate_query_nonce action (publicly available, not a credential) and iterate the popupId parameter. What LIMITS impact: the vulnerability discloses only draft/unpublished post content, so a site with no unpublished or sensitive draft posts has little to lose; it grants no write access, no authentication, and no code execution. The only confirmed remediation path in the evidence is updating to Bricks 2.4.1. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5) describes a remotely reachable, low-complexity flaw needing no privileges and no user interaction, with impact confined to confidentiality - no integrity or availability loss. The description supports every metric: an anonymous attacker reaches the REST endpoint over the network and enumerates content with a simple incrementing parameter. No EPSS probability was supplied, so widespread-exploitation likelihood cannot be quantified here. The CVE is not listed in CISA KEV in the provided data, and no exploit/PoC is marked as confirmed, so there is no evidence of active exploitation. The SSVC/decision signal supplied is vuln.today priority 'this_week' (not act_now or emergency), which aligns with a serious-but-not-fire-drill information-disclosure issue rather than a wormable RCE. Net: this is a genuine priority for sites running Bricks Theme that hold sensitive unpublished content, but its impact ceiling is read-only disclosure of draft posts, not code execution or data modification - a real high-CVSS issue whose practical blast radius is bounded by confidentiality only. Key missing data: EPSS and KEV status were not provided and should be checked before final prioritization. |
| Exploit ScenarioDerived | An anonymous attacker requests a public nonce from the bricks_regenerate_query_nonce action, then sends repeated requests to /wp-json/bricks/v1/load_popup_content with incrementing popupId values. Because the endpoint performs no status or capability check, the server returns the body of draft and unpublished posts, letting the attacker harvest embargoed announcements, unreleased pricing, or other confidential pre-publication content. No authentication, user interaction, or special timing is required; the attack is straightforward and scriptable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 29, 2026
Unauthenticated content disclosure in Bricks Theme 2.4 and earlier for WordPress lets anonymous attackers read draft and unpublished page content through the load_popup_content REST endpoint. Any remote attacker can obtain a public nonce via the bricks_regenerate_query_nonce action and then increment the popupId parameter on /wp-json/bricks/v1/load_popup_content to enumerate confidential drafts across the site, because the endpoint applies no post-status or capability check. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5) confines impact to confidentiality - there is no write access, authentication bypass into administrative functions, or code execution; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the decision label places remediation in the current week rather than as an emergency.
RemediationAI
Update Bricks Theme to 2.4.1, the vendor-released fix documented at https://bricksbuilder.io/release/bricks-2-4-1/; this is the only confirmed remediation path in the available evidence, and no vendor-documented workaround appears in the supplied references. Because the disclosed data is limited to draft and unpublished content, reducing the volume of unpublished material left on the site - publishing, deleting, or moving sensitive drafts out of the WordPress post tables - lowers what an attacker can retrieve while the update is being staged, though it does not close the endpoint. The VulnCheck advisory at https://www.vulncheck.com/advisories/bricks-theme-broken-access-control-via-load-popup-content can be used to confirm the affected route. Note that the endpoint requires no authentication and no non-default configuration, so perimeter filtering of the REST API is a broad measure that risks breaking legitimate theme functionality; prioritize applying 2.4.1 rather than relying on compensating controls.
Affected VersionsENISA
Affected Packages
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 CWE-639, authorization bypass through a user-controlled key, in the WordPress REST API surface exposed by the Bricks theme. The endpoint /wp-json/bricks/v1/load_popup_content accepts a popupId parameter and returns the associated popup content without validating the status of the referenced post or checking the caller's capabilities, so the identifier supplied by the client effectively selects which record is disclosed. Two conditions make this reachable from the internet on default installs: the REST route is registered by default in Bricks 2.4 and earlier, and the bricks_regenerate_query_nonce action hands out a nonce that is public rather than a credential, allowing an anonymous requester to satisfy whatever nonce gating the route applies. Iterating popupId then walks the identifier space, exposing draft and unpublished posts. CPE cpe:2.3:a:bricks:bricks_theme:*:*:*:*:*:*:*:* describes the affected range, bounded at 2.4 and earlier by the vendor's 2.4.1 release. The trigger for the missing check itself is not further described in the available sources; what is confirmed is that no special configuration or privilege is required and that exploitation affects confidentiality only.
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
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Remote, no-auth, no-interaction enumeration of an unprotected REST endpoint (AV:N/AC:L/PR:N/UI:N); confidentiality-only disclosure of all unpublished content justifies C:H with I:N/A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
Bricks Theme 2.4 and before for WordPress contains an unauthenticated broken access control vulnerability in the load_popup_content REST endpoint that allows anonymous attackers to read draft and unpublished page content by supplying a popupId parameter without any status or capability checks. Attackers can obtain a public nonce via the bricks_regenerate_query_nonce action and then increment the popupId value in requests to the /wp-json/bricks/v1/load_popup_content endpoint to enumerate and disclose confidential content from any unpublished post on the site.
Executive ViewAI
A high-severity vulnerability in the Bricks Theme (versions 2.4 and earlier) for WordPress allows unauthenticated attackers to read draft and unpublished page content, potentially exposing confidential information. This affects any organization using the vulnerable theme, and leadership should care because it could lead to data leakage and reputational damage. No active exploitation has been observed, but the risk is significant due to the ease of exploitation.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting access to the vulnerable REST endpoint via WAF, disabling the Bricks Theme if feasible, and implementing custom authorization checks to prevent unauthorized content disclosure.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
The Bricks theme for WordPress is vulnerable to remote code execution due to the theme allowing site editors to include
Unauthenticated attackers can leak password hashes, email addresses, and post metadata from WordPress sites running Bric
Broken access control in the Bricks Builder WordPress plugin/theme through version 2.4.3 lets unauthenticated remote att
The Bricks theme for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.9.6.1. Rate
Reflected cross-site scripting in Bricks Builder WordPress theme through version 1.9.2 to 2.2 enables remote attackers t
The Bricks theme for WordPress is vulnerable to authorization bypass due to a missing capability check on the bricks_sav
Broken Access Control in Bricks Builder for WordPress (versions up to and including 2.1.4) allows subscriber-level authe
The Bricks Builder plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and inc
EUVD-2026-113376
GHSA-g37c-4g9f-f29v
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB