LiveActive security incident?Get immediate response
CVE Record

CVE-2026-84814: WordPress Bricksforge plugin <= 3.1.8.8 - Privilege Escalation vulnerability

Subscriber Privilege Escalation in Bricksforge <= 3.1.8.8 versions.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A flaw in Bricksforge versions through 3.1.8.8 may let an attacker gain elevated WordPress privileges, potentially compromising site data, configuration, and availability. The supplied record rates it critical, but provides limited technical detail.

Executive priority

Treat as an urgent remediation item for internet-facing WordPress sites. Prioritize asset discovery, containment, and vendor-confirmed updating. Investigate potentially affected systems for unauthorized privilege changes rather than assuming an update alone removes prior compromise.

Technical view

CVE-2026-84814 is classified as CWE-266 privilege mismanagement with CVSS 3.1 score 9.8. The description calls it subscriber privilege escalation, while the CVSS vector states no privileges are required. The supplied evidence does not explain the vulnerable mechanism or name a fixed version.

Likely exposure

WordPress sites running Bricksforge 3.1.8.8 or earlier are potentially exposed. Internet accessibility increases practical risk. Sites without Bricksforge, or with a vendor-confirmed unaffected version, are not indicated as vulnerable.

Exploitation context

The supplied sources do not establish active exploitation, and this CVE is not listed as KEV in the bundle. Exploit availability and observed attacks are therefore unknown. The network-accessible, low-complexity CVSS assessment indicates potentially straightforward exploitation if accurate.

Researcher notes

Public detail in the supplied bundle is sparse. The description implies subscriber access, but CVSS reports PR:N; validate this discrepancy before refining attack prerequisites. No vulnerable function, root cause, proof of exploitation, or fixed version is supplied. Avoid inferring authentication requirements or remediation specifics beyond vendor guidance.

Mitigation direction

  • Inventory WordPress sites and identify every installed Bricksforge version.
  • Check Patchstack and Bricksforge guidance for a confirmed fixed release.
  • Update beyond the affected range only after confirming the release is vendor-approved.
  • Disable or remove Bricksforge where safe if no confirmed fix is available.
  • Restrict administrative access and strengthen monitoring until remediation is verified.

Validation and detection

  • Confirm Bricksforge is absent or running a vendor-confirmed unaffected version.
  • Review WordPress users and roles for unexpected accounts or privilege changes.
  • Examine relevant application and security logs for suspicious administrative activity.
  • Rescan affected sites after remediation and document the resulting version.
  • Verify site functionality after updating, disabling, or removing the plugin.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-266: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-84814 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-84814Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Bricksforge.Bricksforgen/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-266 · source CWE mapping

Incorrect Privilege Assignment

Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.