CVE-2025-5760 MEDIUM

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

Vendor Eskapism
Product Simple History – Track, Log, and Audit WordPress Changes
Weakness CWE-256
Published June 6, 2025
Last update April 8, 2026

CVSS base score

4.9/10
Attack vector Network
Attack complexity Low
Privileges required High
User interaction None
Confidentiality High
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Simple History versions up to 5.8.1 contain an information disclosure vulnerability. An authenticated administrator can read sensitive data they should not have access to. The vulnerability requires high-level privileges and does not affect data integrity or availability. Update to a version newer than 5.8.1 to resolve this issue.

What an attacker can do

03Attacker Capabilities

Read sensitive information from the plugin that should be restricted from their access level.

Potential impact on your site

04Site Impact

Administrators with high privileges could access audit logs or configuration data beyond their intended scope.

Conditions required to exploit

05Prerequisites

Attacker must be authenticated as a WordPress administrator or user with equivalent privileges.

Key dates

06Disclosure timeline

June 6, 2025 CVE published
April 8, 2026 Record updated