HeyForm Reflects Any Origin in CORS Responses While Allowing Credentials
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| heyform | heyform | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Heyform | Heyform |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.553% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Heyform
Heyform heyform |
|
| Vendors & Products |
Heyform
Heyform heyform |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | HeyForm before 3.0.0-rc.8 reflects the request Origin header in CORS responses while allowing credentials, enabling cross-origin requests with authentication. Attackers can execute authenticated GraphQL queries from malicious pages visited by logged-in users to access workspaces, projects, forms, submissions, and respondent data, or modify account settings. | |
| Title | HeyForm Reflects Any Origin in CORS Responses While Allowing Credentials | |
| Weaknesses | CWE-942 | |
| References |
|
|
| Metrics |
cvssV3_1
|