# CVE-2025-10050: Developer Loggers for Simple History <= 0.5 - Authenticated (Admin+) Local File Inclusion

> Administrators can exploit a local file inclusion vulnerability to execute arbitrary PHP code or read sensitive data on the server.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-mhmh-2xvp-7mc5

## What is CVE-2025-10050?

CVE-2025-10050 is a medium-severity path traversal vulnerability in eskapism Developer Loggers for Simple History, published on 17 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-10050?


## How do I fix CVE-2025-10050?

No fix has been published for CVE-2025-10050 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10050 being exploited?

There is no known exploitation of CVE-2025-10050 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10050 and fix it if it is affected.

What it is: CVE-2025-10050 is a medium-severity path traversal vulnerability in eskapism Developer Loggers for Simple History, published on 17 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10050 in the wild and no public exploit code.

Affected product: eskapism Developer Loggers for Simple History. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10050/ (Markdown: https://insights.sbomify.com/CVE-2025-10050/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10050
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10050
- OSV: https://osv.dev/vulnerability/CVE-2025-10050

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10050/
Summaries are generated and may contain mistakes; the official description above is the record.