CVE-2026-7459: Simple History – Track, Log, and Audit WordPress Changes <= 5.26.0 - Authenticated (Subscriber+) Account Takeover via Missing Authorization on Event Reaction Endpoint
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.
Security readout for executives and security teams
Plain-English summary
Simple History for WordPress can expose sensitive audit-log context to any logged-in user when experimental features are enabled. In vulnerable versions through 5.26.0, a low-privileged account may read password-reset email content stored in logs, creating a path to administrator account takeover.
Executive priority
Treat this as high priority for WordPress sites with user registration, customer accounts, or many low-privileged users. The non-default setting lowers broad exposure, but administrator takeover is a serious business-impact scenario.
Technical view
The REST event reaction endpoints use a permission check that only confirms authentication, not the per-logger capability checks normally applied to event access. Sources state this can expose SimpleUserLogger password-reset event context, including reset-link material, to Subscriber-level users when experimental features are enabled.
Likely exposure
Exposure is limited to WordPress sites running Simple History up to 5.26.0 with experimental features enabled and untrusted authenticated users, such as Subscribers. Sites without experimental features enabled are described as not meeting the stated exploit precondition.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no source here confirms active exploitation. The attack requires a valid low-privileged account and a non-default experimental setting, but successful abuse can result in administrator account takeover.
Researcher notes
Evidence points to an authorization flaw in REST reaction handlers around event context exposure. Validate exposure by reviewing configuration, plugin version, role model, and whether sensitive password-reset events are logged. Avoid assuming exploit activity or a specific fixed version from this bundle alone.
Mitigation direction
Check vendor guidance and update Simple History when a fixed release is available.
Disable Simple History experimental features unless explicitly required.
Remove or restrict untrusted low-privileged WordPress accounts.
Monitor administrator password-reset events for unusual timing or frequency.
Review Simple History configuration on externally reachable WordPress sites.
Validation and detection
Identify sites running Simple History version 5.26.0 or earlier.
Confirm whether simple_history_experimental_features_enabled is enabled.
Review WordPress roles for untrusted Subscriber-level users.
Check logs for recent administrator password-reset activity.
Track vendor advisories for the fixed version and upgrade status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-640: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-640 · source CWE mapping
Weak Password Recovery Mechanism for Forgotten Password
Weak Password Recovery Mechanism for Forgotten Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.