CVE-2026-107622

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-118190 (ENISA EUVD) · GHSA-7gvp-gcxq-58g5 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The BuddyForms plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.10.5 via a form-type confusion attack through the bf_post_type parameter. This is due to the public frontend submission handler buddyforms_form_response_no_ajax() authorizing logged-out submissions based solely on the target form's public_submit flag while independently trusting the attacker-supplied $_POST['bf_post_type'] to determine the post type of the newly created object — a cross-check introduced in 2.10.2 applies only to existing posts (post_id != 0) and is completely bypassed for new-object creation — combined with the save_post listener buddyforms_edit_form_save_meta_box_data() lacking both a current_user_can() capability check and a form-builder nonce, causing it to unconditionally persist attacker-supplied $_POST['buddyforms_options'] for any newly inserted buddyforms CPT post. This makes it possible for unauthenticated attackers to insert a rogue BuddyForms form configuration with an attacker-controlled new_user_role value into the live global form registry, then submit a registration through that form to create a new WordPress account with administrator-level privileges and achieve full site takeover. Exploitation requires the WordPress site to have "Anyone can register" enabled and at least one public BuddyForms form attached to a page, both of which are standard BuddyForms deployment configurations.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
59
EG Risk 59/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.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
55th
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
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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, and whom BOD 26-04 binds: 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).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

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.

The score's inputs: 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

November 6, 2026

Last Modified

November 6, 2026

Advisory Details (1)

Auto-updated Nov 7, 2026
Patch available. Sources: github_pr.
GitHub pull request Patch Available

fix: take the submission post type from the form and protect form saves

Patch available: Themekraft/buddyforms 2.10.6-beta.1 (PR #779 merged 2026-10-19)

https://github.com/Themekraft/buddyforms/pull/779/files

Vendor Advisories for CVE-2026-107622(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 14× in last 7d / 17× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.7% · 55th percentile
  2. 2026-11-13 03:53 UTCEchelonGraph re-scored
  3. 2026-11-13 03:53 UTCGHSA enrichmentGHSA-7gvp-gcxq-58g5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  5. 2026-11-12 03:14 UTCEchelonGraph re-scored
  6. 2026-11-12 03:14 UTCGHSA enrichmentGHSA-7gvp-gcxq-58g5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  8. 2026-11-11 02:35 UTCEchelonGraph re-scored
  9. 2026-11-11 02:34 UTCGHSA enrichmentGHSA-7gvp-gcxq-58g5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-10 19:10 UTCEchelonGraph re-scored
  11. 2026-11-10 19:10 UTCGHSA enrichmentGHSA-7gvp-gcxq-58g5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  13. 2026-11-09 18:26 UTCEchelonGraph re-scored
  14. 2026-11-09 18:26 UTCGHSA enrichmentGHSA-7gvp-gcxq-58g5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  16. 2026-11-08 17:47 UTCEchelonGraph re-scored
  17. 2026-11-08 17:47 UTCGHSA enrichmentGHSA-7gvp-gcxq-58g5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  19. 2026-11-07 17:07 UTCEchelonGraph re-scored
  20. 2026-11-07 17:07 UTCGHSA enrichmentGHSA-7gvp-gcxq-58g5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  22. 2026-11-06 16:28 UTCEchelonGraph re-scored
  23. 2026-11-06 16:28 UTCGHSA enrichmentGHSA-7gvp-gcxq-58g5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-06 12:27 UTCEchelonGraph re-scored
  25. 2026-11-06 12:04 UTCENISA EUVD ID recordedEUVD-2026-118190 · Source: ENISA EUVD
Show 2 more
  1. 2026-11-06 11:23 UTCEchelonGraph re-scoredFirst assessed: 9.8 CRITICAL
  2. 2026-11-06 11:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-107622?
CVE-2026-107622 is a critical-severity vulnerability; its CVE record was published on November 6, 2026. The BuddyForms plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.10.5 via a form-type confusion attack through the bf_post_type parameter. This is due to the public frontend submission handler buddyforms_form_response_no_ajax() authorizing logged-out…
When was the CVE record for CVE-2026-107622 published?
The CVE record for CVE-2026-107622 was published on November 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 November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-107622 actively exploited?
CVE-2026-107622 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107622?
CVE-2026-107622 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107622?
A fix for CVE-2026-107622 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107622 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-107622?

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

Book a Demo →Browse All CVEs