# CVE-2025-5760: Simple History <= 5.8.1 - Authenticated (Administrator+) Sensitive Information Exposure via Detective Mode

> An authenticated administrator can read logs containing plaintext passwords captured by the Simple History plugin's Detective Mode, leading to credential theft.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-q2wh-799f-g8x3

## What is CVE-2025-5760?

CVE-2025-5760 is a medium-severity vulnerability in eskapism Simple History – Track, Log, and Audit WordPress Changes, published on 6 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Simple History plugin for WordPress is vulnerable to sensitive data exposure via Detective Mode due to improper sanitization within the append_debug_info_to_context() function in versions prior to 5.8.1. When Detective Mode is enabled, the plugin’s logger captures the entire contents of $_POST (and sometimes raw request bodies or $_GET) without redacting any password‐related keys. As a result, whenever a user submits a login form, whether via native wp_login or a third‐party login widget, their actual password is written in clear text into the logs. An authenticated attacker or any user whose actions generate a login event will have their password recorded; an administrator (or anyone with database read access) can then read those logs and retrieve every captured password.

Weakness: CWE-256 (Plaintext Storage of a Password)

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


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

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

## Is CVE-2025-5760 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5760 is a medium-severity vulnerability in eskapism Simple History – Track, Log, and Audit WordPress Changes, published on 6 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5760 in the wild and no public exploit code.

Affected product: eskapism Simple History – Track, Log, and Audit WordPress Changes. 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-5760/ (Markdown: https://insights.sbomify.com/CVE-2025-5760/index.md)
```

## Sources

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

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