Skip to main content

Bricksforge EUVDEUVD-2026-70560

| CVE-2026-84814 CRITICAL
Incorrect Privilege Assignment (CWE-266)
2026-09-03 Patchstack GHSA-26jm-67gf-j9fw
9.8
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Register or obtain subscriber account
  2. Delivery
    Send crafted request to plugin role handler
  3. Exploit
    Bypass authorization check (CWE-266)
  4. Execution
    Elevate account to administrator
  5. Persist
    Install malicious plugin/theme
  6. Impact
    Full site compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Privilege assignment review
Exploitation Conditions

Exploitation targets sites running the Bricksforge plugin at version 3.1.8.8 or earlier. The 'Subscriber Privilege Escalation' designation indicates the attacker needs a low-privileged (subscriber) authenticated account - readily obtainable on sites with open registration enabled, but a limiting factor on sites that disable self-registration. The supplied CVSS vector states PR:N/UI:N (no privileges, no user interaction), which conflicts with the subscriber framing and should be confirmed with the vendor; the realistic prerequisite is a logged-in low-tier account plus the plugin being active. No specific non-default configuration beyond having the plugin installed is described.

Impact

The provided CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H = 9.8) rates this as network-exploitable with no privileges, but the vulnerability title 'Subscriber Privilege Escalation' indicates an authenticated subscriber-level account is the practical precondition - a tension worth verifying with the vendor, since PR:N conflicts with the subscriber framing. On WordPress sites that allow open user registration, a subscriber account is trivial to obtain, so the effective barrier is low and the privilege-escalation-to-admin outcome (which can lead to full site takeover) means any operator running the plugin should treat this as urgent and patch promptly. However, the analysis rests on a single source (Patchstack) with no EPSS probability, no KEV entry, and no public PoC provided, so exploitation likelihood is currently unquantified. Overall this reads as a genuine high-priority WordPress plugin flaw whose real-world risk hinges on whether the site permits self-registration.

Exploit ScenarioDerived

An attacker registers or uses an existing subscriber account on a WordPress site running Bricksforge <= 3.1.8.8, then sends a crafted request to the plugin's role/capability-handling endpoint that lacks a proper authorization check, promoting their own account to administrator. With admin access they install a malicious plugin or theme to achieve full site compromise. No public PoC was identified at time of analysis.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.4% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 03, 2026

Privilege escalation in the Bricksforge WordPress plugin (versions <= 3.1.8.8) lets a low-privileged user elevate their account to higher-privileged roles, per a Patchstack advisory. The flaw (CWE-266, Incorrect Privilege Assignment) carries a CVSS of 9.8 with a network/no-auth vector, though the 'Subscriber Privilege Escalation' label implies a logged-in subscriber account is the realistic starting point. No public exploit code, KEV listing, or EPSS score was provided at time of analysis.

RemediationAI

Upgrade Bricksforge to a version newer than 3.1.8.8 (the fixed release number was not stated in the provided data; confirm the exact patched version via the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/bricksforge/vulnerability/wordpress-bricksforge-plugin-3-1-8-8-privilege-escalation-vulnerability and the plugin's changelog before deploying). As interim compensating controls until patched: disable open user self-registration (Settings > General > 'Anyone can register' unchecked) to remove the low-privilege foothold, temporarily deactivate the Bricksforge plugin if the affected form/workflow feature is not essential (trade-off: breaks any forms or automations built with it), and apply a WAF virtual patch or Patchstack protection to block the exploit request. Audit existing user accounts and roles for unauthorized elevation as a detection step.

Affected VersionsENISA

Bricksforge n/a ≤3.1.8.8

Affected Packages

euvd bricksforge no fix

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

Bricksforge is a form-builder and workflow/automation add-on plugin for the Bricks visual site builder on WordPress, deployed on sites using that page-builder ecosystem. The root cause is CWE-266 (Incorrect Privilege Assignment): the plugin assigns or grants role/capability changes without correctly enforcing who is authorized to perform them, allowing a lower-tier account to obtain capabilities of a higher role. In WordPress this class of bug typically surfaces in AJAX/REST handlers or form-action logic that update user roles, meta, or capabilities without a proper capability check or nonce validation. The affected CPE is cpe:2.3:a:bricksforge.:bricksforge (note the cosmetic trailing dot in the vendor slug); all versions up to and including 3.1.8.8 are listed as vulnerable.

Know when Bricksforge 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 (Patchstack) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Title indicates a subscriber account is required, so PR:L rather than PR:N; escalation to admin yields full C/I/A impact.

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

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

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

DescriptionCVE.org

Subscriber Privilege Escalation in Bricksforge <= 3.1.8.8 versions.

Executive ViewAI

Why It Matters

Bricksforge WordPress plugin versions 3.1.8.8 and below contain a critical privilege escalation flaw enabling low-privilege subscriber accounts to gain full administrative access. Organizations using this plugin face immediate risk of unauthorized site control, data access, and system compromise, with no vendor patch currently available to address the vulnerability. Immediate remediation is required to prevent account takeover and site compromise.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include disabling the Bricksforge plugin if features are not business-critical. If functionality is required, restrict the Subscriber user role to minimum necessary permissions via WordPress role management or hardening plugins, enforce multi-factor authentication for all privileged accounts, and implement comprehensive logging and alerting for role and permission changes. Conduct weekly audits of admin and editor accounts for unauthorized modifications. While these controls reduce risk, they do not fully eliminate the vulnerability-vendor patch availability is essential for complete remediation.

Threat Intelligence Overview

EPSS Score
0.4%
Top 70% exploitable
Prevalence
Low
niche add-on for the Bricks builder, limited WordPress footprint
Social Media
1
Sightings
Data Quality
4 sources
Confidence: Medium

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 CRITICAL
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
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
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

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

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

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