LiveActive security incident?Get immediate response
CVE Record

CVE-2025-54725: WordPress Golo Theme <= 1.7.0 - Broken Authentication Vulnerability

Authentication Bypass Using an Alternate Path or Channel vulnerability in uxper Golo golo allows Authentication Abuse.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-2025-54725 is a critical authentication bypass in the WordPress Golo theme. A remote unauthenticated attacker may be able to abuse an alternate authentication path, creating risk to site control, data confidentiality, and service availability. The source bundle does not confirm active exploitation.

Executive priority

Treat as urgent for any internet-facing WordPress site using Golo. The business risk is potential unauthorized site access and control, but exploitation in the wild is not confirmed by the supplied evidence.

Technical view

The CVE describes CWE-288, Authentication Bypass Using an Alternate Path or Channel, affecting uxper Golo through version 1.7.0. CVSS 3.1 is 9.8 with network attack vector, low complexity, no privileges, and no user interaction. Published affected metadata is sparse, so validate exposure against installed theme versions.

Likely exposure

Public WordPress sites running the uxper Golo theme version 1.7.0 or earlier are the likely exposure set. Prioritize production, externally reachable, and business-critical WordPress properties first.

Exploitation context

CISA KEV status is false in the bundle, and no provided source confirms active exploitation. The CVSS vector indicates the issue is remotely reachable without credentials or user interaction, which makes exposure time important.

Researcher notes

Do not assume details beyond the CVE and Patchstack listing. The affected record is limited, with description identifying Golo through 1.7.0. Validate locally and monitor source updates before asserting exploitability details or fixed versions.

Mitigation direction

  • Inventory all WordPress sites for the Golo theme and installed version.
  • Check uxper, WordPress theme distribution, and Patchstack guidance for a fixed release.
  • Upgrade, remove, or disable vulnerable Golo installations per vendor guidance.
  • Review authentication, administrator, and theme-related logs for suspicious activity.
  • Apply compensating access controls where immediate remediation is not possible.

Validation and detection

  • Confirm whether Golo is installed or active on each WordPress site.
  • Record exact Golo version and compare against <= 1.7.0.
  • Verify remediation by confirming the vulnerable version is no longer present.
  • Check monitoring for unusual logins, new administrators, or unexpected site changes.
  • Track Patchstack and CVE records for updated affected-version or fix details.
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-288: 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

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-2025-54725 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-2025-54725Attack 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-288 · source CWE mapping

Authentication Bypass Using an Alternate Path or Channel

Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.