Simple History <= 5.8.1 - Authenticated (Administrator+) Sensitive Information Exposure via Detective Mode
Strategic Overview
- Status
- Patched in 5.8.2
- Affected Plugin
- Simple History – Track, Log, and Audit WordPress Changes
- Affected Version
<= 5.8.1- CVSS
- 4.9Medium
- Weakness type
- CWE-256 · Plaintext Storage of a Password
- CVE
CVE-2025-5760
At a glance
CVE-2025-5760 is a medium-severity Plaintext Storage of a Password vulnerability in the Simple History WordPress plugin, affecting versions <= 5.8.1. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 5.8.2; sites on affected versions should update now. Disclosed June 2025, reported by Blair Crawford.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-256: Plaintext Storage of a Password
The product stores a password in plaintext within resources such as memory or files.
Remediation
Update to version 5.8.2, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Simple History 5.8.2 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in Simple History – Track, Log, and Audit WordPress Changes
- 7.5CVE-2026-7459: Simple History Account Takeover
CVE-2026-7459 - 6.0CVE-2022-45350: Simple History <= 3.3.1 CSV Injection
CVE-2022-45350 - 5.3CVE-2026-39473: Simple History <= 5.24.0 Information Exposure
CVE-2026-39473 - 5.3Simple History <= 1.0.7 Sensitive Information Disclosure
- 4.3Simple History Plugin < 2.7.5 Sensitive Information Disclosure
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C