# 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.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-9jh7-hmgx-8gq5

## 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 (Weak Password Recovery Mechanism for Forgotten Password)

## 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.

## 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:

- CVE-2026-7459 Simple History Missing Authorization Account Takeover Exploit (github_poc): https://github.com/izxci/CVE-2026-7459

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7459 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-7459 in the wild and no public exploit code.

Affected product: eskapism Simple History – Track, Log, and Audit WordPress Changes. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7459/ (Markdown: https://insights.sbomify.com/CVE-2026-7459/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7459
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7459
- OSV: https://osv.dev/vulnerability/CVE-2026-7459

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7459/
Summaries are generated and may contain mistakes; the official description above is the record.