CVE-2026-6228

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-15. NVD baseline CVSS 8.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 week
8.8EG
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.8%CVSS: 8.8Exploit: 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 CNA (Wordfence) lists shabti Frontend Admin by DynamiApps versions up to and including 3.28.36 as affected. No release containing a fix is confirmed on record.

The Frontend Admin by DynamiApps plugin for WordPress is vulnerable to Privilege Escalation in versions up to and including 3.28.36. This is due to insufficient authorization checks in the role field update mechanism combined with overly permissive capabilities for the admin_form post type. The admin_form custom post type uses 'capability_type' => 'page', which grants editors the ability to create and edit forms. When an editor creates an edit_user form, they can manipulate the form configuration to include 'administrator' in the role_options array by directly submitting POST data to wp-admin/post.php, bypassing the UI restrictions in feadmin_get_user_roles(). When the form is subsequently submitted, the pre_update_value() function in class-role.php only validates that the submitted role exists in the form's role_options array (lines 107-110), but fails to verify that the current user has permission to assign that specific role. This makes it possible for unauthenticated attackers to first register as editors (via a public new_user form), then create an edit_user form with administrator in the allowed roles, and finally use that form to escalate their own privileges to administrator.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.8% × 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.8%
EPSS %ILE
54th
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

May 15, 2026

Last Modified

May 15, 2026

References (5)

Vendor Advisories for CVE-2026-6228(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 13× in last 7d / 29× 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 243 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 146 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-6228?
CVE-2026-6228 is a high-severity vulnerability; its CVE record was published on May 15, 2026. The Frontend Admin by DynamiApps plugin for WordPress is vulnerable to Privilege Escalation in versions up to and including 3.28.36. This is due to insufficient authorization checks in the role field update mechanism combined with overly permissive capabilities for the adminform post type. The…
When was the CVE record for CVE-2026-6228 published?
The CVE record for CVE-2026-6228 was published on May 15, 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 May 15, 2026; the record at its source may have been updated since.
Is CVE-2026-6228 actively exploited?
CVE-2026-6228 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-6228?
CVE-2026-6228 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-6228?
No fix for CVE-2026-6228 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 shabti Frontend Admin by DynamiApps versions up to and including 3.28.36 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-6228 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-6228?

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

Book a Demo →Browse All CVEs