CVE-2026-7459: CWE-640 Weak Password Recovery Mechanism for Forgotten Password in eskapism Simple History – Track, Log, and Audit WordPress Changes
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.
AI Analysis
Technical Summary
The Simple History plugin for WordPress suffers from an authenticated account takeover vulnerability (CVE-2026-7459) due to weak permission enforcement on event reaction endpoints (react_to_event() / unreact_to_event()). These endpoints use get_items_permissions_check() which only verifies that the user is logged in, without enforcing per-logger capability checks. Consequently, a Subscriber-level user can POST to the reaction endpoint with specific parameters to read the full context of any event, including password reset emails logged by SimpleUserLogger. By triggering a password reset for an administrator and enumerating event IDs, the attacker can extract the reset key from the logged event and complete the password reset process, gaining administrator access. Exploitation requires the experimental features option (simple_history_experimental_features_enabled) to be enabled by an administrator, which is off by default. No official patch or remediation guidance has been published as of the data provided.
Potential Impact
Successful exploitation allows an authenticated low-privilege user (Subscriber) to take over administrator accounts by obtaining password reset links from logged events. This results in full compromise of the WordPress site, including confidentiality, integrity, and availability impacts as reflected in the CVSS score of 7.5 (High). The vulnerability requires the experimental feature to be enabled, limiting exposure to some extent.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should ensure that the experimental features option (simple_history_experimental_features_enabled) remains disabled to prevent exploitation. Restricting Subscriber-level users from accessing the event reaction endpoints or disabling the Simple History plugin temporarily may also reduce risk.
CVE-2026-7459: CWE-640 Weak Password Recovery Mechanism for Forgotten Password in eskapism Simple History – Track, Log, and Audit WordPress Changes
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.
CVSS v3.1
Score 7.5high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Simple History plugin for WordPress suffers from an authenticated account takeover vulnerability (CVE-2026-7459) due to weak permission enforcement on event reaction endpoints (react_to_event() / unreact_to_event()). These endpoints use get_items_permissions_check() which only verifies that the user is logged in, without enforcing per-logger capability checks. Consequently, a Subscriber-level user can POST to the reaction endpoint with specific parameters to read the full context of any event, including password reset emails logged by SimpleUserLogger. By triggering a password reset for an administrator and enumerating event IDs, the attacker can extract the reset key from the logged event and complete the password reset process, gaining administrator access. Exploitation requires the experimental features option (simple_history_experimental_features_enabled) to be enabled by an administrator, which is off by default. No official patch or remediation guidance has been published as of the data provided.
Potential Impact
Successful exploitation allows an authenticated low-privilege user (Subscriber) to take over administrator accounts by obtaining password reset links from logged events. This results in full compromise of the WordPress site, including confidentiality, integrity, and availability impacts as reflected in the CVSS score of 7.5 (High). The vulnerability requires the experimental feature to be enabled, limiting exposure to some extent.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should ensure that the experimental features option (simple_history_experimental_features_enabled) remains disabled to prevent exploitation. Restricting Subscriber-level users from accessing the event reaction endpoints or disabling the Simple History plugin temporarily may also reduce risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-04-29T18:01:43.775Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1ab2aee29bf47b5015dfa7
Added to database: 05/30/2026, 09:49:34 UTC
Last enriched: 06/06/2026, 21:02:21 UTC
Last updated: 07/16/2026, 07:47:30 UTC
Views: 146
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.