Simple History – Track, Log, and Audit WordPress Changes <= 5.26.0 - Authenticated (Subscriber+) Account Takeover via Missing Authorization on Event Reaction Endpoint
Strategic Overview
- Status
- Patched in 5.27.0
- Affected Plugin
- Simple History – Track, Log, and Audit WordPress Changes
- Affected Version
<= 5.26.0- CVSS
- 7.5High
- Weakness type
- CWE-640 · Weak Password Recovery Mechanism for Forgotten Password
- CVE
CVE-2026-7459
At a glance
CVE-2026-7459 is a high-severity Weak Password Recovery Mechanism for Forgotten Password vulnerability in the Simple History WordPress plugin, affecting versions <= 5.26.0. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.27.0; sites on affected versions should update now. Disclosed May 2026, reported by lhking.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-640: Weak Password Recovery Mechanism for Forgotten Password
Simple History <= 5.26.0 carries this weakness at react_to_event(), and reaching it takes an account at Subscriber level or above. A weak password recovery mechanism means the path that lets someone back into an account without their password is easier to complete than the password itself.
An attacker takes over an account through the recovery flow without ever seeing the password, and on an administrator account that is full control of the site. For Simple History the fix is 5.27.0: builds <= 5.26.0 are affected, anything from 5.27.0 onward is not.
Remediation
Update to version 5.27.0, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Simple History 5.27.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Simple History – Track, Log, and Audit WordPress Changes
- 6.0CVE-2022-45350: Simple History <= 3.3.1 CSV Injection
CVE-2022-45350 - 5.3CVE-2026-39473: Simple History <= 5.24.0 Information Exposure
CVE-2026-39473 - 5.3Simple History <= 1.0.7 Sensitive Information Disclosure
- 4.9CVE-2025-5760: Simple History <= 5.8.1 Sensitive Information Exposure
CVE-2025-5760 - 4.3Simple History Plugin < 2.7.5 Sensitive Information Disclosure
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C