VYPR
Unrated severityNVD Advisory· Published Jun 16, 2026

WordPress Getaway theme < 1.8 - Local File Inclusion vulnerability

CVE-2026-39547

Description

Unauthenticated local file inclusion in the Getaway WordPress theme prior to version 1.8 allows attackers to read sensitive files, including database credentials, potentially leading to complete site compromise.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Unauthenticated local file inclusion in the Getaway WordPress theme prior to version 1.8 allows attackers to read sensitive files, including database credentials, potentially leading to complete site compromise.

Vulnerability

The Getaway WordPress theme versions prior to 1.8 contain an unauthenticated Local File Inclusion (LFI) vulnerability. The flaw resides in a file inclusion mechanism that does not properly validate user-supplied input, allowing an attacker to specify arbitrary file paths without requiring any authentication. The code path is reachable under default configuration; no special settings are needed to trigger the vulnerability [1].

Exploitation

An attacker can exploit this vulnerability from any network position by sending a crafted HTTP request to the vulnerable endpoint. No authentication or user interaction is required. The attacker simply includes a path to a local file (e.g., /etc/passwd or wp-config.php) in the request parameter, and the server includes and outputs the contents of that file [1].

Impact

Successful exploitation allows an attacker to read arbitrary local files on the target server. This can expose sensitive information such as database credentials, site configuration, and other secrets stored in files on the web server. In many cases, leaked database credentials (found in wp-config.php) can enable a full database takeover, potentially leading to complete administrative control over the WordPress site [1].

Mitigation

Users must update the Getaway theme to version 1.8 or later, which contains the fix for this vulnerability. As of the publication date (2026-06-16), no other workaround has been documented. Site owners unable to update immediately are advised to consult their hosting provider or apply a virtual patch or Web Application Firewall (WAF) rule to block LFI attempts [1].

AI Insight generated on Jun 17, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.