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-12824: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in tharkun69 Player Leaderboard

0
High
VulnerabilityCVE-2025-12824cvecve-2025-12824cwe-22
Published: Fri Dec 12 2025 (12/12/2025, 03:20:44 UTC)
Source: CVE Database V5
Vendor/Project: tharkun69
Product: Player Leaderboard

Description

The Player Leaderboard plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.0.2 via the 'player_leaderboard' shortcode. This is due to the plugin using an unsanitized user-supplied value from the shortcode's 'mode' attribute in a call to include() without proper path validation. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary PHP files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve full remote code execution if combined with file upload capabilities.

AI-Powered Analysis

AILast updated: 12/19/2025, 05:00:36 UTC

Technical Analysis

CVE-2025-12824 is a path traversal vulnerability classified under CWE-22, affecting the Player Leaderboard plugin for WordPress, specifically versions up to and including 1.0.2, with confirmed impact on version 1.0.0. The vulnerability stems from the plugin's handling of the 'mode' attribute in the 'player_leaderboard' shortcode, where user-supplied input is passed directly to a PHP include() function without proper sanitization or validation. This lack of input validation allows an authenticated attacker with at least Contributor-level privileges to manipulate the path parameter to include arbitrary files from the server filesystem. By including malicious PHP files, attackers can execute arbitrary code within the context of the web server, potentially bypassing access controls, accessing sensitive data, or achieving full remote code execution if combined with file upload mechanisms. The vulnerability does not require user interaction beyond authentication and has a CVSS 3.1 base score of 8.8, indicating high severity, with network attack vector, low attack complexity, and no user interaction required. Although no known exploits are currently in the wild, the ease of exploitation and potential impact make this a critical concern for WordPress sites using this plugin. The absence of official patches at the time of publication necessitates immediate attention to mitigation strategies.

Potential Impact

For European organizations, this vulnerability poses a significant risk, especially for those relying on WordPress sites with the Player Leaderboard plugin installed. Successful exploitation can lead to unauthorized code execution, resulting in data breaches, website defacement, or full server compromise. This can disrupt business operations, damage reputation, and lead to regulatory non-compliance under GDPR due to potential exposure of personal data. Attackers could leverage this vulnerability to pivot within internal networks, escalate privileges, or deploy ransomware. The risk is amplified in sectors with high-value targets such as finance, healthcare, and government institutions across Europe. Additionally, the widespread use of WordPress in Europe increases the potential attack surface. Organizations with Contributor-level user roles on affected sites are particularly vulnerable, as these accounts can be leveraged to exploit the flaw. The lack of public exploits currently provides a window for proactive defense, but the threat landscape may evolve rapidly.

Mitigation Recommendations

Given the absence of an official patch, European organizations should implement immediate compensating controls. First, restrict Contributor-level and higher user roles to trusted personnel only, minimizing the risk of malicious insiders or compromised accounts exploiting the vulnerability. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the 'mode' parameter in the 'player_leaderboard' shortcode. Conduct thorough audits of installed WordPress plugins and remove or disable the Player Leaderboard plugin if not essential. If the plugin is necessary, consider applying manual code hardening by sanitizing and validating the 'mode' attribute inputs to prevent path traversal. Monitor logs for unusual file inclusion attempts or unexpected PHP file executions. Limit file upload capabilities and ensure strict validation on uploaded content to reduce the risk of combining LFI with file upload for remote code execution. Regularly update WordPress core and plugins to the latest versions once patches become available. Finally, implement robust access controls and multi-factor authentication to reduce the risk of account compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-06T19:06:04.782Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693b9182650da22753edbadb

Added to database: 12/12/2025, 3:52:34 AM

Last enriched: 12/19/2025, 5:00:36 AM

Last updated: 2/5/2026, 11:16:43 AM

Views: 48

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