Simple History – Track, Log, and Audit WordPress Changes
simple-history · plugin
Known security vulnerabilities for Simple History – Track, Log, and Audit WordPress Changes. Find out in seconds which version runs on your site with WP Lens.
4 known vulnerabilities
1 exploitable without logging in · 1 with public exploit code · latest May 30, 2026
Listed on wordpress.org · latest 5.35.0 · last updated Oct 7, 2026 · 300K+ installs
wordpress.org status checked on Oct 9, 2026
Vulnerabilities
- High 8.8
CVE-2022-45350login required≤ 3.3.1
WordPress Simple History Plugin <= 3.3.1 is vulnerable to CSV Injection
- High 7.5
CVE-2026-7459subscriber+≤ 5.26.0
Simple History – Track, Log, and Audit WordPress Changes <= 5.26.0 - Authenticated (Subscriber+) Account Takeover via Missing Authorization on Event Reaction En
- Medium 5.3
CVE-2026-39473unauthenticated≤ 5.24.0
WordPress Simple History plugin <= 5.24.0 - Sensitive Data Exposure vulnerability
- Medium 4.9
CVE-2025-5760admin≤ 5.8.1
Simple History <= 5.8.1 - Authenticated (Administrator+) Sensitive Information Exposure via Detective Mode
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).