HeyForm
HeyForm: Uploaded HTML files are served as text/html on the app origin with no CSP — stored XSS
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.0.1
Fixed in 3.0.1
Mitigation
Upgrade heyform to 3.0.1 or later.
References
- Vendor advisory github.com/heyform/heyform/security/advisories…
- Patch github.com/heyform/heyform/commit/849f7101d437…
- Release notes github.com/heyform/heyform/releases/tag/v3.0.1
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.