CVE-2026-47278

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (21st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source

Also known asEUVD-2026-130392 (ENISA EUVD)Source: ENISA EUVD

6.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Frappe is a full-stack web application framework. Prior to 15.108.0 and 16.18.3, the add_comment handler in frappe/templates/includes/comments/comments.py trusts the client-provided comment_by and comment_email fields. A caller can submit chosen identity metadata that is stored with a comment, causing the comment to appear to originate from another name or email address. This issue is fixed in versions 15.108.0 and 16.18.3.

CVSS
6.9
EG Score
6.9MEDIUMlow confidence
EG Risk
31
EG Risk 31/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)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.3%
EPSS %ILE
21st
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 (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 19, 2026

Last Modified

November 19, 2026

Advisory Details (9)

Auto-updated Nov 19, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available

v16.18.3

Patch available: frappe/frappe v16.18.3

https://github.com/frappe/frappe/releases/tag/v16.18.3
GitHub release Patch Available

v15.108.0

Patch available: frappe/frappe v15.108.0

https://github.com/frappe/frappe/releases/tag/v15.108.0
GitHub commit Patch Available

commit c1cc4cc4ef3a (frappe/frappe)

Patch available: frappe/frappe v16.35.0 (contains commit c1cc4cc4ef3a)

https://github.com/frappe/frappe/commit/c1cc4cc4ef3ac2151fff330edd32aa96c13d4118
GitHub commit Patch Available

commit 7bcbf72f283f (frappe/frappe)

Patch available: frappe/frappe v15.121.2 (contains commit 7bcbf72f283f)

https://github.com/frappe/frappe/commit/7bcbf72f283fc68d9abe783fcc2219386f14e9ef
GitHub commit

commit 2d930e2d3747 (frappe/frappe)

Fix landed in frappe/frappe commit 2d930e2d3747 — awaiting tagged release

https://github.com/frappe/frappe/commit/2d930e2d3747012cc8a8c8fbdccaf8c2c5070391
GitHub pull request Patch Available

fix(comments): override comment_by and comment_email (backport #39373)

Patch available: frappe/frappe v16.35.0 (PR #39380 merged 2026-05-19)

https://github.com/frappe/frappe/pull/39380
GitHub pull request Patch Available

fix(comments): override comment_by and comment_email (backport #39373)

Patch available: frappe/frappe v15.121.2 (PR #39379 merged 2026-05-19)

https://github.com/frappe/frappe/pull/39379
GitHub pull request

fix(comments): override comment_by and comment_email

Fix merged in frappe/frappe PR #39373 on 2026-05-19 — awaiting tagged release

https://github.com/frappe/frappe/pull/39373
GitHub advisoryMentions a patch (unverified)

Comment Spoofing · Advisory · frappe/frappe · GitHub

https://github.com/frappe/frappe/security/advisories/GHSA-89m3-vggh-725v

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 4× 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 → 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-21 16:39 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-11-20 16:37 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-11-19 19:30 UTCEchelonGraph re-scored
  4. 2026-11-19 18:48 UTCEchelonGraph re-scored
  5. 2026-11-19 18:03 UTCENISA EUVD ID recordedEUVD-2026-130392 · Source: ENISA EUVD
  6. 2026-11-19 17:29 UTCEchelonGraph re-scored
  7. 2026-11-19 16:43 UTCEchelonGraph re-scoredFirst assessed: 6.9 MEDIUM
  8. 2026-11-19 16:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-47278?
CVE-2026-47278 is a medium-severity vulnerability; its CVE record was published on November 19, 2026. Frappe is a full-stack web application framework. Prior to 15.108.0 and 16.18.3, the add_comment handler in frappe/templates/includes/comments/comments.py trusts the client-provided comment_by and comment_email fields. A caller can submit chosen identity metadata that is stored with a comment,…
When was the CVE record for CVE-2026-47278 published?
The CVE record for CVE-2026-47278 was published on November 19, 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 19, 2026; the record at its source may have been updated since.
Is CVE-2026-47278 actively exploited?
CVE-2026-47278 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47278?
CVE-2026-47278 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-47278?
A fix for CVE-2026-47278 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-47278?

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