LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32388: WordPress GLB theme <= 1.2.2 - Broken Access Control vulnerability

Missing Authorization vulnerability in linethemes GLB glb allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects GLB: from n/a through <= 1.2.2.

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32388 affects the WordPress GLB theme through version 1.2.2. It is a broken access control issue where a logged-in user may perform actions they should not be authorized to perform. The expected business impact is limited data integrity or availability risk, not confirmed data theft.

Executive priority

Treat as a medium-priority WordPress exposure. Prioritize sites that allow public registration, many contributors, or customer-facing content management. Do not treat as confirmed mass exploitation based on the provided sources.

Technical view

The CVE describes missing authorization in linethemes GLB, mapped to CWE-862. CVSS 3.1 is 5.4 with network access, low complexity, low privileges required, no user interaction, and low integrity and availability impact. Public details do not identify the vulnerable function or a confirmed fixed version.

Likely exposure

Exposure is most likely on WordPress sites using the GLB theme at version 1.2.2 or earlier. Exploitation requires an authenticated user account, reducing risk compared with unauthenticated WordPress flaws.

Exploitation context

The CVE is not listed as CISA KEV in the provided data, and no active exploitation is cited. The issue is still relevant where untrusted users can register, log in, or obtain low-privilege WordPress accounts.

Researcher notes

Public information is sparse. The CVE identifies missing authorization but does not provide endpoint-level details, exploit status, or a named patch. Validation should focus on asset exposure, theme versioning, account trust boundaries, and monitoring vendor updates.

Mitigation direction

  • Inventory WordPress sites for the GLB theme and its installed version.
  • Restrict or remove untrusted low-privilege accounts where possible.
  • Check the vendor or Patchstack entry for fixed-version guidance.
  • Apply any vendor-published update or mitigation when available.
  • Review access controls around theme-related administrative actions.

Validation and detection

  • Confirm whether GLB is installed on each WordPress site.
  • Record the GLB theme version and compare it with version 1.2.2.
  • Review user registration and low-privilege account exposure.
  • Check logs for unusual authenticated changes affecting site content or availability.
  • Monitor the CVE and Patchstack pages for updated remediation details.
Prepared
Confidence
medium
Sources
3

Public sources used

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-32388 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
5.4 (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:L

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

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2026-32388Attack 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:L

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
linethemesGLBglb, 0unaffected
Weakness

CWE details

CWE-862

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