WordPress plugin
Simple History – Track, Log, and Audit WordPress Changes security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 6 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
- Critical0
- High1
- Medium5
- Low0
All Simple History – Track, Log, and Audit WordPress Changes vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High7.5 | Authenticated (Subscriber+) Account Takeover via Missing Authorization on Event Reaction Endpoint ≤5.26.0Update to 5.27.0 | CVE-2026-7459 |
- High7.5Authenticated (Subscriber+) Account Takeover via Missing Authorization on Event Reaction Endpoint
≤5.26.0Update to 5.27.0
Simple History – Track, Log, and Audit WordPress Changes: common questions
Does Simple History – Track, Log, and Audit WordPress Changes have known vulnerabilities?
Yes. VulnCrest Radar lists 6 known vulnerabilities in Simple History – Track, Log, and Audit WordPress Changes: 1 high, 5 medium. None are known to affect version null.
How do I check which version of Simple History – Track, Log, and Audit WordPress Changes I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Simple History – Track, Log, and Audit WordPress Changes vulnerability?
CVE-2026-7459, published May 29, 2026: Simple History – Track, Log, and Audit WordPress Changes <= 5.26.0 - Authenticated (Subscriber+) Account Takeover via Missing Authorization on Event Reaction Endpoint. Severity: High (CVSS 7.5).
Is any Simple History – Track, Log, and Audit WordPress Changes vulnerability listed in CISA KEV?
No. None of the known Simple History – Track, Log, and Audit WordPress Changes vulnerabilities is currently listed in the CISA KEV catalog.