HeyForm is an open-source form builder. Prior to version 3.0.0-rc.7, the /api/upload endpoint allows unauthenticated file uploads including SVG files. Uploaded SVGs are stored in the static assets directory and served with Content-Type: image/svg+xml by Express's serve-static middleware, allowing an attacker to achieve stored cross-site scripting (XSS) on the heyform domain without any authentication. Version 3.0.0-rc.7 contains a patch for the issue.
CVE-2026-45797
This medium-severity CVE scores 6.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.4
- EG Score
- 6.4(medium)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
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 computedSeverity64% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 33%
- KEV
- Not listed
Published
July 20, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jul 20, 2026Stored XSS via Unauthenticated SVG File Upload · Advisory · heyform/heyform · GitHub
https://github.com/heyform/heyform/security/advisories/GHSA-m94h-jxvc-hhchcommit 144240e5545d (heyform/heyform)
Patch available: heyform/heyform v3.0.0-rc.7 (contains commit 144240e5545d)
https://github.com/heyform/heyform/commit/144240e5545d10fd9e120d05ccb402a6d7064674Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-28 09:55 UTCEG score recompute
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 10:20 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 10:48 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:16 UTCEG score recompute
- 2026-07-22 23:37 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 19:31 UTCEG score recompute
- 2026-07-20 16:37 UTCEG score recompute
- 2026-07-20 16:03 UTCEG score recompute
- 2026-07-20 16:02 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-79 · CWE-434
Frequently asked(5)
What is CVE-2026-45797?
When was CVE-2026-45797 disclosed?
Is CVE-2026-45797 actively exploited?
What is the CVSS score of CVE-2026-45797?
How do I remediate CVE-2026-45797?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-45797
Is Your Infrastructure Affected by CVE-2026-45797?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.