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

CVE-2025-15020 is a path traversal vulnerability in the Gotham Block Extra Light WordPress plugin, affecting all versions up to 1. 5. 0. Authenticated users with contributor-level access or higher can exploit this flaw via the 'ghostban' shortcode to read arbitrary files on the server. This can expose sensitive information, impacting confidentiality without affecting integrity or availability. The vulnerability requires low attack complexity and no user interaction beyond authentication. Although no known exploits are currently in the wild, the medium CVSS score of 6. 5 reflects a significant risk. European organizations using this plugin on WordPress sites should prioritize patching or mitigating this issue. Countries with high WordPress adoption and active web publishing sectors are most at risk.

AI-Powered Analysis

AILast updated: 01/21/2026, 20:45:14 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 hosting server. This arbitrary file read flaw can expose sensitive server files such as configuration files, credentials, or other private data, compromising confidentiality. The attack vector is remote network-based (AV:N), with low attack complexity (AC:L), requiring privileges (PR:L) but no user interaction (UI:N). The scope is unchanged (S:U), and the impact is high on confidentiality (C:H), with no impact on integrity or availability (I:N, A:N). Although no public exploits are known, the vulnerability poses a significant risk due to the ease of exploitation by authenticated users and the potential sensitivity of exposed data. The vulnerability was reserved in late 2025 and published in early 2026, with no patches currently available, necessitating immediate mitigation steps. The plugin’s widespread use in WordPress sites makes this a relevant threat vector, especially for organizations relying on contributor-level access for content management.

Potential Impact

For European organizations, this vulnerability can lead to unauthorized disclosure of sensitive information stored on web servers running the Gotham Block Extra Light plugin. This includes configuration files, database credentials, or other private data that could facilitate further attacks such as privilege escalation or lateral movement. The impact is primarily on confidentiality, potentially exposing personal data protected under GDPR, which could result in regulatory penalties and reputational damage. Since the vulnerability requires contributor-level access, insider threats or compromised contributor accounts pose a significant risk. The lack of impact on integrity and availability reduces the risk of service disruption but does not diminish the severity of data exposure. Organizations with active WordPress sites using this plugin, especially those in sectors like media, education, or government, where contributor roles are common, are at heightened risk. The medium severity rating reflects the balance between required privileges and the potential data exposure consequences.

Mitigation Recommendations

Immediate mitigation should focus on restricting contributor-level access to trusted users only and auditing existing contributor accounts for suspicious activity. Disable or restrict the use of the 'ghostban' shortcode until a patch is available. Implement web application firewall (WAF) rules to detect and block path traversal attempts targeting the shortcode parameters. Monitor server logs for unusual file access patterns indicative of exploitation attempts. Employ the principle of least privilege by limiting file system permissions for the web server user to only necessary directories, reducing the impact of arbitrary file reads. Regularly update WordPress and plugins, and subscribe to vendor advisories for patch releases. Consider isolating critical WordPress instances or migrating to alternative plugins with better security track records if immediate patching is not feasible. Conduct security awareness training for contributors to recognize phishing or credential compromise attempts that could lead to exploitation.

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/21/2026, 8:45:14 PM

Last updated: 2/7/2026, 5:15:20 PM

Views: 23

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