CVE-2026-7459 Missing authorization in Simple History – Track, Log, and Audit WordPress Changes
Authenticated subscribers can take over administrator accounts by reading password reset keys from logs due to missing authorization checks on event reaction endpoints.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-7459?
CVE-2026-7459 is a high-severity missing authorization vulnerability in eskapism Simple History – Track, Log, and Audit WordPress Changes, published on 30 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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 register get_items_permissions_check() as their permission_callback, which only verifies the requester is logged in and does not enforce the per-logger capability checks normally applied by Log_Query. As a result, a Subscriber-level user can POST to /wp-json/simple-history/v1/events/<id>/react with the _fields=context query parameter and read the full context of any Simple History event — including SimpleUserLogger entries that record the full password-reset email body (reset URL with the reset key) for any user. The attacker triggers a password reset for an administrator via the lost-password form, brute-forces recent event IDs through the reaction endpoint to read the resulting user_requested_password_reset_link event, extracts the reset key from context.message, and completes the password reset to take over the administrator account. Exploitation requires an administrator to have first enabled the experimental features option (simple_history_experimental_features_enabled), which is not the default.
Weakness: CWE-640
Which versions are affected by CVE-2026-7459?
How do I fix CVE-2026-7459?
No fix has been published for CVE-2026-7459 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-7459 being exploited?
There is no known exploitation of CVE-2026-7459 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-9jh7-hmgx-8gq5.