LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27051: WordPress Golo theme <= 1.7.0 - Privilege Escalation vulnerability

Incorrect Privilege Assignment vulnerability in uxper Golo golo allows Privilege Escalation.This issue affects Golo: from n/a through <= 1.7.0.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-27051 is a critical privilege escalation issue in the WordPress Golo theme through version 1.7.0. The published scoring indicates a remote, unauthenticated attacker may gain high-impact access without user interaction. Sites using this theme should be prioritized for review, especially public WordPress deployments.

Executive priority

High priority for organizations running WordPress with the Golo theme. The vulnerability is critical and potentially unauthenticated, but provided sources do not confirm exploitation or a specific patch. Immediate inventory and vendor-guided remediation are warranted.

Technical view

The issue is described as Incorrect Privilege Assignment in uxper Golo, affecting versions through 1.7.0. CVSS 3.1 is 9.8 with AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Public details do not include exploit mechanics, affected functions, or a named fixed version in the provided sources.

Likely exposure

Exposure is likely limited to WordPress sites running the Golo theme version 1.7.0 or earlier. Internet-facing WordPress sites have the highest business risk because the CVSS vector indicates network access and no authentication requirement.

Exploitation context

The provided sources do not state active exploitation, and the CVE is not listed as KEV in the supplied bundle. Treat exploitation potential as high because the vulnerability is unauthenticated, low complexity, and impacts confidentiality, integrity, and availability.

Researcher notes

Public information is sparse. The CVE identifies CWE-266 and privilege escalation in Golo through 1.7.0, but does not provide root cause details or safe validation indicators. Avoid assuming a fixed version unless confirmed by vendor or Patchstack updates.

Mitigation direction

  • Inventory WordPress sites for the Golo theme and installed version.
  • Check Patchstack and the vendor for current remediation guidance.
  • Update or replace the theme if a fixed release is available.
  • Restrict administrative access and review user accounts for unexpected privilege changes.
  • Ensure recent backups exist before making theme or WordPress changes.

Validation and detection

  • Confirm whether the active or installed theme is Golo.
  • Record the installed Golo version on each WordPress site.
  • Flag any Golo installation at version 1.7.0 or earlier.
  • Review WordPress users for unexpected administrator or elevated roles.
  • Monitor web and application logs for suspicious account or role 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 · 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-27051 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
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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-27051Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
uxperGologolo, 0unaffected
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.