Quick answers
- Is CVE-2026-102615 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102615 being exploited in the wild.
- How severe is CVE-2026-102615?
- High severity, with a CVSS score of 7.6, published 5 November 2026.
- Which products and versions are affected?
- HeyForm before 3.0.1.
- Is there a fix for CVE-2026-102615?
- Yes: fixed in 3.0.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-102615 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-102615?
- Check whether you run HeyForm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.0.1
Technical details
The /api/upload endpoint accepts files with a client-controlled MIME type while preserving HTML filenames, then serves them as text/html with Content-Security-Policy disabled from the static/upload path. This allows stored XSS attacks where malicious HTML executes on the HeyForm origin with the victim's session credentials, enabling access to /graphql to read or modify account data. The vulnerability also affects unauthenticated public form submissions via formId, openToken, and file/signature field IDs.
Affected products
- HeyForm HeyForm before 3.0.1
Timeline
- 2026-11-05: disclosed