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-10050: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in eskapism Developer Loggers for Simple History

0
Medium
VulnerabilityCVE-2025-10050cvecve-2025-10050cwe-22
Published: Wed Sep 17 2025 (09/17/2025, 01:49:16 UTC)
Source: CVE Database V5
Vendor/Project: eskapism
Product: Developer Loggers for Simple History

Description

The Developer Loggers for Simple History plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 0.5 via the enabled_loggers parameter. This makes it possible for authenticated attackers, with Administrator-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 code execution in cases where .php file types can be uploaded and included.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 18:04:02 UTC

Technical Analysis

CVE-2025-10050 is a path traversal vulnerability classified under CWE-22 affecting the Developer Loggers for Simple History plugin for WordPress. This vulnerability arises from improper limitation of a pathname to a restricted directory, specifically through the enabled_loggers parameter. An authenticated attacker with administrator-level access can exploit this flaw to perform Local File Inclusion (LFI), allowing them to include arbitrary .php files from the server. This can lead to arbitrary PHP code execution, bypassing access controls and potentially exposing sensitive data or enabling full system compromise. The vulnerability affects all versions up to and including 0.5 of the plugin. The attack vector is network-based (remote), but requires high privileges (administrator) and no user interaction. The CVSS 3.1 score is 6.6, reflecting a medium severity due to the combination of high impact but limited exploitability. No patches or known exploits are currently reported, but the risk remains significant for affected installations. The vulnerability highlights the importance of proper input validation and path restriction in web applications, especially plugins that handle file inclusion.

Potential Impact

The impact of CVE-2025-10050 is significant for organizations using the affected WordPress plugin. Successful exploitation allows attackers with administrator privileges to execute arbitrary PHP code on the server, which can lead to full system compromise. This includes bypassing access controls, stealing sensitive data, modifying or deleting data, and potentially pivoting to other parts of the network. Given WordPress's widespread use, especially in small to medium businesses and content-driven websites, the vulnerability could lead to defacement, data breaches, or ransomware deployment. However, the requirement for administrator-level access limits the attack surface to insiders or attackers who have already compromised credentials. The vulnerability could also be leveraged in multi-stage attacks where initial access is gained through other means. The absence of known exploits in the wild suggests limited current exploitation but does not diminish the potential risk if weaponized.

Mitigation Recommendations

To mitigate CVE-2025-10050, organizations should immediately update the Developer Loggers for Simple History plugin to a patched version once available. In the absence of a patch, restrict administrator access to trusted personnel only and enforce strong authentication mechanisms such as multi-factor authentication (MFA). Review and limit the ability to upload or place arbitrary PHP files on the server to reduce the risk of malicious file inclusion. Implement web application firewalls (WAFs) with rules to detect and block path traversal attempts targeting the enabled_loggers parameter. Conduct regular audits of installed plugins and remove any unnecessary or outdated components. Additionally, monitor logs for unusual file inclusion or execution activity and isolate affected systems promptly if exploitation is suspected. Developers should apply secure coding practices to validate and sanitize all input parameters related to file paths.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-09-05T18:55:18.588Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68ca1a3d571b2840ff0172da

Added to database: 9/17/2025, 2:17:33 AM

Last enriched: 2/27/2026, 6:04:02 PM

Last updated: 3/22/2026, 4:36:56 AM

Views: 51

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses