WordPress Bricksforge plugin <= 3.1.8.8 - Privilege Escalation vulnerability

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Bricksforge./Bricksforge (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Bricksforge./Bricksforge.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 3, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 3, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 3, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• HP Support Assistant – Potential Escalation of PrivilegeSame generic ecosystem
• c-ares : Use-after-free / double-free in c-ares query-completion handling, remotely triggerable via ares_getaddrinfo() over TCPSame generic ecosystem
• Waku: Cross-Origin CSRF on RSC Server Action DispatchSame generic ecosystem
• Waku: Open Redirect via `unstable_redirect` HelperSame generic ecosystem
• GeoNetwork vulnerable to Remote Code Execution via unsafe Saxon XSLT processor configuration in formatterSame generic ecosystem
• Unauthenticated file upload via missing authorization on formatter upload endpointSame generic ecosystem