LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32408: WordPress Brizy plugin <= 2.7.23 - Broken Access Control vulnerability

Missing Authorization vulnerability in themefusecom Brizy brizy allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Brizy: from n/a through <= 2.7.23.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32408 affects the WordPress Brizy plugin through version 2.7.23. It is a broken access control issue, meaning a logged-in user may perform an action they should not be authorized to perform. The recorded impact is limited to integrity, with no confidentiality or availability impact stated.

Executive priority

Treat as a routine but timely WordPress plugin remediation. The business risk is lower than remote code execution or data theft, but unauthorized changes can affect site integrity, brand trust, and operational control. Prioritize internet-facing WordPress sites and environments with many contributor-level users.

Technical view

The CVE describes CWE-862 Missing Authorization in themefusecom Brizy. CVSS 3.1 is 4.3: network exploitable, low complexity, low privileges required, no user interaction, unchanged scope, low integrity impact only. Public details do not identify the vulnerable function, endpoint, or exact unauthorized action.

Likely exposure

Exposure is likely limited to WordPress sites with the Brizy plugin installed at version 2.7.23 or earlier, and where an attacker can authenticate with a low-privilege account. Sites without Brizy, or running versions outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not marked as CISA KEV. The CVSS vector indicates exploitation requires network access and low privileges, but not user interaction. No public exploit steps or proof-of-concept details are provided in the cited sources.

Researcher notes

Public information is sparse. The record identifies missing authorization in Brizy through 2.7.23 but does not disclose the affected capability, vulnerable endpoint, patch commit, or exploitability details beyond CVSS. Avoid assuming unauthenticated access or broader impact than low integrity modification.

Mitigation direction

  • Inventory WordPress sites for the Brizy plugin and record installed versions.
  • Prioritize sites running Brizy version 2.7.23 or earlier.
  • Check Brizy, WordPress.org, or Patchstack guidance for the fixed version or vendor workaround.
  • Update Brizy beyond the affected range if a fixed release is available.
  • Remove or disable Brizy where it is unused and cannot be promptly remediated.

Validation and detection

  • Confirm whether Brizy is installed on each WordPress site.
  • Verify the installed Brizy version against the affected range: through 2.7.23.
  • Review WordPress user roles for unnecessary low-privilege accounts.
  • Check vendor or Patchstack advisories for updated remediation status.
  • Monitor site audit logs for unexpected content or configuration changes.
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 · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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
cve · low confidence lookup

CVE-2026-32408 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
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

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
0Timeline events
0ADP providers
2Source links

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-32408Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
themefusecomBrizybrizy, 0unaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

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