CVE-2026-7459

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-30. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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//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
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

May 30, 2026

Last Modified

July 22, 2026

References (12)

Vendor Advisories for CVE-2026-7459(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 73× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 240 total refreshes for this CVE.

  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-09-01 04:40 UTCEPSS rescore
  6. 2026-08-30 19:18 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:42 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 14:47 UTCEPSS rescore
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-25 04:08 UTCEG score recompute
  14. 2026-08-25 04:08 UTCGHSA enrichment
  15. 2026-08-24 14:18 UTCEPSS rescore
  16. 2026-08-23 14:03 UTCEG score recompute
  17. 2026-08-23 14:03 UTCGHSA enrichment
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-21 14:58 UTCEG score recompute
  21. 2026-08-21 14:58 UTCGHSA enrichment
  22. 2026-08-20 22:56 UTCEPSS rescore
  23. 2026-08-20 22:28 UTCGHSA enrichment
  24. 2026-08-20 10:23 UTCEG score recompute
  25. 2026-08-20 10:23 UTCGHSA enrichment
Show 75 more
  1. 2026-08-19 17:04 UTCEPSS rescore
  2. 2026-08-18 13:49 UTCEPSS rescore
  3. 2026-08-18 13:49 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-17 06:49 UTCGHSA enrichment
  6. 2026-08-16 16:26 UTCEG score recompute
  7. 2026-08-16 16:26 UTCGHSA enrichment
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 04:37 UTCEG score recompute
  11. 2026-08-16 04:37 UTCGHSA enrichment
  12. 2026-08-16 02:15 UTCEPSS rescore
  13. 2026-08-15 16:48 UTCEG score recompute
  14. 2026-08-15 16:48 UTCGHSA enrichment
  15. 2026-08-15 01:31 UTCEPSS rescore
  16. 2026-08-15 00:04 UTCGHSA enrichment
  17. 2026-08-14 12:15 UTCGHSA enrichment
  18. 2026-08-14 00:26 UTCEG score recompute
  19. 2026-08-14 00:26 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 10:54 UTCGHSA enrichment
  22. 2026-08-12 23:05 UTCEG score recompute
  23. 2026-08-12 23:05 UTCGHSA enrichment
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-12 11:17 UTCGHSA enrichment
  26. 2026-08-11 23:20 UTCEG score recompute
  27. 2026-08-11 23:20 UTCGHSA enrichment
  28. 2026-08-11 13:43 UTCEPSS rescore
  29. 2026-08-11 11:31 UTCEG score recompute
  30. 2026-08-11 11:31 UTCGHSA enrichment
  31. 2026-08-11 00:00 UTCEPSS rescore
  32. 2026-08-10 23:40 UTCGHSA enrichment
  33. 2026-08-10 07:03 UTCGHSA enrichment
  34. 2026-08-09 19:13 UTCEG score recompute
  35. 2026-08-09 19:13 UTCGHSA enrichment
  36. 2026-08-09 13:47 UTCEPSS rescore
  37. 2026-08-09 07:25 UTCGHSA enrichment
  38. 2026-08-08 19:36 UTCEG score recompute
  39. 2026-08-08 19:36 UTCGHSA enrichment
  40. 2026-08-08 16:37 UTCEPSS rescore
  41. 2026-08-08 07:45 UTCGHSA enrichment
  42. 2026-08-07 19:56 UTCEG score recompute
  43. 2026-08-07 19:56 UTCGHSA enrichment
  44. 2026-08-07 08:08 UTCGHSA enrichment
  45. 2026-08-06 20:19 UTCEG score recompute
  46. 2026-08-06 20:19 UTCGHSA enrichment
  47. 2026-08-06 13:47 UTCEPSS rescore
  48. 2026-08-06 08:30 UTCGHSA enrichment
  49. 2026-08-05 20:41 UTCEG score recompute
  50. 2026-08-05 20:41 UTCGHSA enrichment
  51. 2026-08-05 19:17 UTCEPSS rescore
  52. 2026-08-05 19:17 UTCEPSS rescore
  53. 2026-08-04 22:57 UTCEG score recompute
  54. 2026-08-04 22:57 UTCGHSA enrichment
  55. 2026-08-04 15:10 UTCEPSS rescore
  56. 2026-08-04 10:39 UTCEPSS rescore
  57. 2026-08-04 03:42 UTCGHSA enrichment
  58. 2026-08-03 15:54 UTCEG score recompute
  59. 2026-08-03 15:54 UTCGHSA enrichment
  60. 2026-08-03 10:36 UTCEPSS rescore
  61. 2026-08-03 01:22 UTCGHSA enrichment
  62. 2026-08-02 13:34 UTCEG score recompute
  63. 2026-08-02 13:34 UTCGHSA enrichment
  64. 2026-08-02 02:27 UTCEPSS rescore
  65. 2026-08-02 01:45 UTCGHSA enrichment
  66. 2026-08-01 13:53 UTCEG score recompute
  67. 2026-08-01 13:53 UTCGHSA enrichment
  68. 2026-08-01 04:16 UTCEPSS rescore
  69. 2026-07-31 19:05 UTCGHSA enrichment
  70. 2026-07-31 05:50 UTCEG score recompute
  71. 2026-07-31 05:50 UTCGHSA enrichment
  72. 2026-07-30 16:28 UTCEPSS rescore
  73. 2026-07-30 01:30 UTCEPSS rescore
  74. 2026-07-29 11:30 UTCEG score recompute
  75. 2026-07-29 11:30 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-7459?
CVE-2026-7459 is a high vulnerability published on May 30, 2026. 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 (reacttoevent() / unreacttoevent()). The endpoints register…
When was CVE-2026-7459 disclosed?
CVE-2026-7459 was first published in the National Vulnerability Database on May 30, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7459 actively exploited?
CVE-2026-7459 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.9% of all scored CVEs.
What is the CVSS score of CVE-2026-7459?
CVE-2026-7459 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-7459?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7459, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-7459

Explore →

Is Your Infrastructure Affected by CVE-2026-7459?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.