CVE Details
Basic Information
| Title | Simple History <= 5.8.1 - Authenticated (Administrator+) Sensitive Information Exposure via Detective Mode |
|---|---|
| Type | cve |
| Published | 2025-06-06T11:13:16.129Z |
| Last Seen |
Product Information
| Vendor | eskapism |
|---|---|
| Product | Simple History – Track, Log, and Audit WordPress Changes |
| Version | * |
CVSS Information
| Base Score | 4.9 (MEDIUM) |
|---|---|
| Attack Vector | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| Confidentiality Impact | |
| Integrity Impact | |
| Availability Impact |
AI Analysis
| AI Description | The Simple History WordPress plugin exposes sensitive data by logging passwords in clear text when Detective Mode is enabled. This affects versions prior to 5.8.1, allowing attackers to retrieve stored passwords from logs. |
|---|---|
| AI Severity | Medium |
| Vendor | WordPress Community |
| Product | Simple History |
| Affected Version | <5.8.1 |
Affected Products
- eskapism Simple History – Track, Log, and Audit WordPress Changes *
Additional Information
| CVE List | |
|---|---|
| CWE List | CWE-256 |
| Bulletin Family |
References
- https://www.wordfence.com/threat-intel/vulnerabilities/id/b6364415-da02-4236-b635-d8fbd27faa33?source=cve
- https://simple-history.com/support/detective-mode/
- https://wordpress.org/plugins/simple-history/#developers
- https://github.com/bonny/WordPress-Simple-History/issues/546
- https://github.com/bonny/WordPress-Simple-History/commit/68eab0cab6882eafef4bfece884093eeda5ac018
- https://wordpress.org/support/topic/security-vulnerability-passwords-stored-as-plain-text-in-logs/
- https://plugins.trac.wordpress.org/changeset/3267487/
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.