HeyForm is an open-source form builder. Prior to 3.0.1, /api/upload accepts a file according to the client-controlled multipart file.mimetype while retaining an HTML filename, and static/upload serves the resulting file as text/html with contentSecurityPolicy: false. An ordinary user can therefore upload active HTML that executes on the HeyForm origin when a victim opens its returned URL. The same-origin script can access /graphql with the victim's session and read or modify data available to that account. The code also permits upload requests tied to an active public form through formId, openToken, and a fieldId belonging to a file or signature question, although the advisory did not fully verify that unauthenticated path end to end. This issue is fixed in version 3.0.1.
CVE-2026-102615
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (16th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-117549 (ENISA EUVD)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 7.6
- EG Score
- 7.6HIGHmedium confidence
- EG Risk
- 50EG Risk 50/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)Severity76% × 45%Impact severity (EG Severity): CVSS 7.6 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.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 public PoC (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
- 16th
- 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 (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). 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; Track* at high (mission-essential systems).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 low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (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 5, 2026
Last Modified
November 9, 2026
Advisory Details (3)
Auto-updated Nov 5, 2026v3.0.1
Patch available: heyform/heyform v3.0.1
https://github.com/heyform/heyform/releases/tag/v3.0.1commit 849f7101d437 (heyform/heyform)
Patch available: heyform/heyform v3.0.1 (contains commit 849f7101d437)
https://github.com/heyform/heyform/commit/849f7101d4370b29e716b2d7ee14a86c2f598f3aUploaded HTML files are served as text/html on the app origin with no CSP — stored XSS · Advisory · heyform/heyform · GitHub
https://github.com/heyform/heyform/security/advisories/GHSA-pxw5-pjrc-j758Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 10× 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.
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-09 23:48 UTCEchelonGraph re-scored
- 2026-11-09 22:41 UTCEchelonGraph re-scored
- 2026-11-09 22:20 UTCEchelonGraph re-scored
- 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-05 17:04 UTCENISA EUVD ID recordedEUVD-2026-117549 · Source: ENISA EUVD
- 2026-11-05 16:27 UTCEchelonGraph re-scored
- 2026-11-05 15:39 UTCEchelonGraph re-scoredFirst assessed: 7.6 HIGH
- 2026-11-05 15:38 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-102615?
When was the CVE record for CVE-2026-102615 published?
Is CVE-2026-102615 actively exploited?
What is the CVSS score of CVE-2026-102615?
How do I remediate CVE-2026-102615?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-102615
Is Your Infrastructure Affected by CVE-2026-102615?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.