Golo – City Travel Guide WordPress Theme Vulnerability (High) – CVE…

Golo – City Travel Guide WordPress Theme Vulnerability (High) – CVE…

by | Feb 10, 2026 | Themes

Attack Vectors

Golo – City Travel Guide WordPress Theme (slug: golo) versions prior to 1.7.5 are affected by a High-severity Local File Inclusion (LFI) vulnerability (CVE-2026-23975, CVSS 7.5). This issue requires an attacker to already be authenticated with at least Contributor permissions.

In practical terms, this means the risk is highest for organizations that allow multiple users to publish or upload content (e.g., marketing teams, agencies, partners, or contractors). If an attacker gains access to a Contributor (or higher) account—through password reuse, phishing, or a compromised vendor login—they may be able to force the site to load files from the server in unintended ways.

Because WordPress sites often grant Contributor access for content workflows, this vulnerability is especially relevant to marketing-led sites where user access is distributed beyond IT.

Security Weakness

The core weakness is Local File Inclusion: the theme can be manipulated to include server files that were never meant to be loaded through the web application. According to the advisory, this can allow authenticated attackers (Contributor+) to include and execute arbitrary files on the server, enabling access control bypass, sensitive data exposure, and potentially code execution if a file containing PHP code can be included.

This is particularly concerning when an attacker can upload a file that appears “safe” (such as an image) but can still be included in a way that results in executing embedded code, depending on how the vulnerable functionality processes included files.

Remediation: Update Golo – City Travel Guide WordPress Theme to version 1.7.5 or newer. Reference: Wordfence vulnerability record.

Technical or Business Impacts

Business risk: With High severity and the potential for code execution, this vulnerability can turn a marketing website into an entry point for broader harm—especially if the site integrates with analytics tools, CRM forms, email platforms, payment processors, or single sign-on.

Potential impacts include: exposure of sensitive data stored on or accessible through the site (including configuration details and credentials), unauthorized changes to site content (brand damage, SEO spam, malicious redirects), service disruption, and incident response costs. If exploited, it can also trigger compliance concerns depending on what data is accessible and whether the site supports lead capture or customer accounts.

Operational reality: The requirement for a Contributor-level account means this is not purely a “random internet” risk; it’s a privileged user risk. That makes identity hygiene and user access governance especially important for marketing organizations with multiple collaborators.

Similar Attacks

Local File Inclusion and related file-handling flaws have been used in real-world WordPress compromises, including:

Elementor Pro vulnerabilities (Wordfence report) — demonstrates how widely used WordPress components can become high-value targets when flaws enable unauthorized access or code execution paths.

Contact Form 7 unrestricted file upload issue (Wordfence report) — illustrates the business risk when attackers can upload files and then leverage application behavior to execute or abuse them.

CVE-2026-23975 record — official CVE entry for this issue in Golo – City Travel Guide WordPress Theme.

Vantage Vulnerability (Medium) – CVE-2026-5070

Attack Vectors CVE-2026-5070 is a Medium severity vulnerability (CVSS 6.4) affecting the Vantage WordPress theme (slug: vantage) in versions up to and including 1.20.32. It enables authenticated users with Contributor access or higher to inject malicious script into a...

WP Docs Vulnerability (Medium) – CVE-2026-3878

Attack Vectors CVE-2026-3878 is a Medium severity Stored Cross-Site Scripting (XSS) vulnerability (CVSS 6.4) affecting the WP Docs WordPress plugin (wp-docs) in versions 2.2.9 and below. The issue is exploitable by an authenticated user with Subscriber-level access or...

WPFore Subscribers