Radar sectionsDatabase
Check my site
WordPress plugin

Simple History <= 5.8.1 — Authenticated (Administrator+) Sensitive Information Exposure via Detective Mode

CVE-2025-5760Published · Updated

Action summary

Affected: ≤5.8.1Update to 5.8.2 or newer

All remediation steps
Severity
Medium4.9
CVSS
4.9
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:H Privileges required
High
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:N Integrity
None
A:N Availability
None
Weakness
CWE-256 Plaintext Storage of a Password
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Simple History – Track, Log, and Audit WordPress Changes simple-history

  1. Affected≤ 5.8.1
  2. Patched in5.8.2

Update to 5.8.2 or newer.

You are affected if you run ≤ 5.8.1. Version 5.8.2 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Simple History – Track, Log, and Audit WordPress Changes.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 5.8.2, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Simple History – Track, Log, and Audit WordPress Changes to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Blair Crawford.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Simple History – Track, Log, and Audit WordPress Changes

All 6
More vulnerabilities in Simple History – Track, Log, and Audit WordPress Changes
SeverityVulnerabilityCVEPublished
High7.5Authenticated (Subscriber+) Account Takeover via Missing Authorization on Event Reaction Endpoint
≤5.26.0Update to 5.27.0
CVE-2026-7459
Medium5.3Unauthenticated Information Exposure
≤5.24.0Update to 5.24.1
CVE-2026-39473
Medium6.0Authenticated (Subscriber+) CSV Injection
≤3.3.1Update to 3.4.0
CVE-2022-45350
Medium4.3Sensitive Information Disclosure
≤2.7.4Update to 2.7.5
—
Medium5.3Sensitive Information Disclosure
≤1.0.7Update to 1.0.8
—

Timeline

  1. CVE published

    Severity medium, CVSS 4.9

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?