Simple History – Track, Log, and Audit WordPress Changes vulnerabilities
Plugin slug simple-history · 6 known vulnerabilities · latest disclosed 2026-05-29 · WordPress.org page
Every listed vulnerability has a fix. Version 5.27.0 or later is not affected by any of them. If your site runs an older version, update it.
1 of 6 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Simple History – Track, Log, and Audit WordPress Changes
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| High 7.5 | <= 5.26.0 | 5.27.0 | CVE-2026-7459 | 2026-05-29 | Advisory |
| Medium 5.3 | <= 5.24.0 | 5.24.1 | CVE-2026-39473 | 2026-03-22 | Advisory |
| Medium 4.9 | <= 5.8.1 | 5.8.2 | CVE-2025-5760 | 2025-06-05 | Advisory |
| Medium 6 | <= 3.3.1 | 3.4.0 | CVE-2022-45350 | 2023-02-02 | Advisory |
| Medium 4.3 | <= 2.7.4 | 2.7.5 | none | 2016-07-28 | Advisory |
| Medium 5.3 | <= 1.0.7 | 1.0.8 | none | 2014-08-01 | Advisory |
Check if a site is affected
Enter a site address to see which version of Simple History – Track, Log, and Audit WordPress Changes and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Simple History – Track, Log, and Audit WordPress Changes plugin safe to use?
All 6 known issues are fixed in current versions (5.27.0 or later). Keeping it updated is what matters.
How do I check which version of Simple History – Track, Log, and Audit WordPress Changes my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.