CVE-2026-8732

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-29. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 1.9%CVSS: 9.8Exploit: Public PoCExposed 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 CNA (Wordfence) lists flippercode WP Maps Pro versions up to and including 6.0.4 as affected. No release containing a fix is confirmed on record.

The WP Maps Pro plugin for WordPress is vulnerable to Privilege Escalation via Administrator Account Creation in all versions up to, and including, 6.1.0. This is due to the wpgmp_temp_access_ajax AJAX action being registered with wp_ajax_nopriv_ and protected only by a nonce check using the fc-call-nonce nonce, which is publicly embedded into every frontend page via wp_localize_script as the nonce field of the wpgmp_local JavaScript object, rendering the check ineffective as an access control mechanism. This makes it possible for unauthenticated attackers to invoke the wpgmp_temp_access_support handler with check_temp=false, which unconditionally creates a new WordPress user with the hardcoded role of administrator via wp_insert_user() and returns a magic login URL that, when visited, calls wp_set_auth_cookie() to fully authenticate the attacker as the newly created administrator, resulting in complete site takeover.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.9%
EPSS %ILE
78th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-18). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend 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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

May 29, 2026

Last Modified

July 21, 2026

Vendor Advisories for CVE-2026-8732(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 19× in last 7d / 44× 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 97 of 403 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 306 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(5 references)

Public exploit code is referenced for this CVE (4 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • GitHub PoCfientix/CVE-2026-8732-PoC
    Published Sep 8, 2026

    CVE-2026-8732 | WP Maps Pro <= 6.1.0 Unauth Admin Creation

    Open source ↗
  • Nucleihttp/cves/2026/CVE-2026-8732.yaml
    Published Jul 20, 2026

    WP Maps Pro (wp-google-map-gold) <= 6.1.0 - Unauthenticated Administrator Account Creation

    Open source ↗
  • GitHub PoCp3Nt3st3r-sTAr/CVE-2026-8732-POC
    Published Jun 1, 2026
    Open source ↗
  • GitHub PoCJenderal92/CVE-2026-8732
    Published May 30, 2026

    WP Maps Pro <= 6.1.0 - Unauthenticated Privilege Escalation via Administrator Account Creation to wpgmp_temp_access_ajax AJAX Action

    Open source ↗
  • GitHub PoCzycoder0day/CVE-2026-8732
    Published May 30, 2026

    CVE-2026-8732 | WP Maps Pro <= 6.1.0 | Unauthenticated Privilege Escalation

    Open source ↗

Frequently asked(5)

What is CVE-2026-8732?
CVE-2026-8732 is a critical-severity vulnerability; its CVE record was published on May 29, 2026. The WP Maps Pro plugin for WordPress is vulnerable to Privilege Escalation via Administrator Account Creation in all versions up to, and including, 6.1.0. This is due to the wpgmptempaccessajax AJAX action being registered with wpajaxnopriv and protected only by a nonce check using the…
When was the CVE record for CVE-2026-8732 published?
The CVE record for CVE-2026-8732 was published on May 29, 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 21, 2026; the record at its source may have been updated since.
Is CVE-2026-8732 actively exploited?
CVE-2026-8732 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% probability of exploitation in the next 30 days (78th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8732?
CVE-2026-8732 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-8732?
No fix for CVE-2026-8732 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 CNA (Wordfence) lists flippercode WP Maps Pro versions up to and including 6.0.4 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-8732 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-8732?

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