CVE-2026-9851

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-06-06. A secondary CVSS source baseline 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
7.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.2Exploit: None knownExposed services: Not assessed

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

The CVE record's description, written by its CNA (Wordfence), states the affected versions: "The Booking Package plugin for WordPress is vulnerable to Privilege Escalation via Account Takeover in versions up to, and including, 1.7.16." No release containing a fix is confirmed on record.

The Booking Package plugin for WordPress is vulnerable to Privilege Escalation via Account Takeover in versions up to, and including, 1.7.16. This is due to a missing capability check on the 'updateUser' branch of the package_app_action AJAX endpoint, where the handler only validates a nonce and the dispatcher invokes Schedule::updateUser() with the $administrator argument hard-coded to 1, bypassing the only owner-restriction check inside that function and allowing the target user to be determined solely by attacker-supplied input passed directly to wp_update_user(). This makes it possible for authenticated attackers, with Editor-level access and above, to change the email address and password of any account, including Administrator accounts, resulting in a full site takeover.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
33
EG Risk 33/100

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 (value × EchelonGraph’s weight)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 6, 2026

Last Modified

July 23, 2026

References (5)

Vendor Advisories for CVE-2026-9851(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 10× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 270 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 170 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9851?
CVE-2026-9851 is a high-severity vulnerability; its CVE record was published on June 6, 2026. The Booking Package plugin for WordPress is vulnerable to Privilege Escalation via Account Takeover in versions up to, and including, 1.7.16. This is due to a missing capability check on the 'updateUser' branch of the packageappaction AJAX endpoint, where the handler only validates a nonce and the…
When was the CVE record for CVE-2026-9851 published?
The CVE record for CVE-2026-9851 was published on June 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-9851 actively exploited?
CVE-2026-9851 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9851?
CVE-2026-9851 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-9851?
No fix for CVE-2026-9851 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's description, written by its CNA (Wordfence), states the affected versions: "The Booking Package plugin for WordPress is vulnerable to Privilege Escalation via Account Takeover in versions up to, and including, 1.7.16." No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-9851 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-9851?

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

Book a Demo →Browse All CVEs