The Simple History – Track, Log, and Audit WordPress Changes plugin for WordPress is vulnerable to authenticated (Subscriber+) account takeover in all versions up to, and including, 5.26.0 via the event reaction endpoints (react_to_event() / unreact_to_event()). The endpoints reg...
Product
wordpress simple-history vulnerabilities
6 published CVES affecting wordpress simple-history, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 2
- Medium
- 4
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress simple-history CVEs
Newest publication first
-
HighCVSS 7.5 EPSS 0.59%
-
CVE-2026-39473 WordPress Simple History plugin <= 5.24.0 - Sensitive Data Exposure vulnerability
PublishedMediumCVSS 5.3 EPSS 0.25%Insertion of Sensitive Information Into Sent Data vulnerability in Pär Thernström Simple History simple-history allows Retrieve Embedded Sensitive Data.This issue affects Simple History: from n/a through <= 5.24.0.
-
MediumCVSS 4.9 EPSS 0.47%
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...
-
HighCVSS 8.8 EPSS 0.83%
Improper Neutralization of Formula Elements in a CSV File vulnerability in Pär Thernström Simple History – user activity log, audit tool.This issue affects Simple History – user activity log, audit tool: from n/a through 3.3.1.
-
MediumCVSS 4.3
The Simple History plugin for WordPress is vulnerable to Sensitive Data Exposure in versions up to, and including, 2.7.4 via the ajax_simple_history_filters_search_user function. This can allow authenticated attackers to extract sensitive data including logged in usernames and th...
-
MediumCVSS 5.3
The Simple History plugin for WordPress is vulnerable to Sensitive Data Exposure in versions up to, and including, 1.0.7 via the 'rss_secret' parameter. This can allow unauthenticated attackers to view sensitive information from the RSS feed.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.