Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-15020: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in gothamdev Gotham Block Extra Light

0
Medium
VulnerabilityCVE-2025-15020cvecve-2025-15020cwe-22
Published: Wed Jan 14 2026 (01/14/2026, 05:28:10 UTC)
Source: CVE Database V5
Vendor/Project: gothamdev
Product: Gotham Block Extra Light

Description

The Gotham Block Extra Light plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 1.5.0 via the 'ghostban' shortcode. This makes it possible for authenticated attackers, with contributor-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

AI-Powered Analysis

AILast updated: 01/14/2026, 06:06:30 UTC

Technical Analysis

CVE-2025-15020 is a path traversal vulnerability classified under CWE-22 found in the Gotham Block Extra Light plugin for WordPress, affecting all versions up to and including 1.5.0. The vulnerability arises from improper limitation of pathname inputs in the 'ghostban' shortcode functionality, allowing authenticated users with contributor-level privileges or higher to read arbitrary files on the web server. This arbitrary file read capability can expose sensitive information such as configuration files, credentials, or other protected data stored on the server. The attack vector requires network access and authentication but no additional user interaction, making it a relatively straightforward exploit for insiders or compromised contributor accounts. The CVSS v3.1 base score is 6.5, reflecting a medium severity with high confidentiality impact, no impact on integrity or availability, low attack complexity, and privileges required. No patches or exploit code are currently publicly available, but the vulnerability's presence in a widely used CMS plugin poses a significant risk if weaponized. The flaw stems from insufficient validation or sanitization of input parameters used in file path construction within the shortcode handler, enabling directory traversal sequences to access files outside intended directories.

Potential Impact

For European organizations, this vulnerability can lead to unauthorized disclosure of sensitive server-side files, including credentials, private keys, or proprietary information, potentially facilitating further attacks such as privilege escalation or lateral movement. Organizations relying on WordPress with the Gotham Block Extra Light plugin installed are at risk, especially those with multiple contributors or editors who have authenticated access. The confidentiality breach could result in compliance violations under GDPR if personal data is exposed. Although the vulnerability does not affect system integrity or availability directly, the information disclosure can undermine trust and lead to secondary attacks. The risk is heightened in sectors with sensitive data such as finance, healthcare, and government institutions. Since exploitation requires contributor-level access, insider threats or compromised contributor accounts are primary concerns. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as exploit code could emerge.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Immediately audit and restrict contributor-level access to trusted personnel only, minimizing the attack surface. 2) Monitor and log usage of the 'ghostban' shortcode to detect anomalous or unauthorized file access attempts. 3) Employ web application firewalls (WAFs) with custom rules to detect and block directory traversal patterns in shortcode parameters. 4) Isolate WordPress installations and sensitive files using strict file system permissions to limit exposure even if traversal occurs. 5) Regularly update the Gotham Block Extra Light plugin once a patch is released by the vendor. 6) Conduct internal security awareness training to reduce risks from compromised contributor accounts. 7) Consider disabling or removing the plugin if it is not essential to reduce attack vectors. 8) Implement intrusion detection systems to identify suspicious file read activities. These measures go beyond generic advice by focusing on access control, monitoring, and containment tailored to this vulnerability's characteristics.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-22T04:47:03.843Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69672e018330e067168f4018

Added to database: 1/14/2026, 5:47:45 AM

Last enriched: 1/14/2026, 6:06:30 AM

Last updated: 1/14/2026, 5:12:02 PM

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats