External risk intelligence

HeyForm Stored Cross-Site Scripting Vulnerability Allows Account Takeover

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2026-35198

HeyForm is a web-based form builder application. Such tools are typically deployed as web-facing services accessible to users over the internet, making the application's interface and its associated features commonly reachable via public-facing web infrastructure.

Cross-site Scripting

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability exists in the HeyForm form builder that could allow a user with limited access to take over an entire account. This occurs when a malicious script is injected into a form and then executed by an account owner viewing the form, potentially granting the attacker elevated privileges.

  • Injected scripts can lead to account takeover.
  • Protects against unauthorized privilege escalation.
  • Confirm relevance and understand potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker with low privileges could inject malicious JavaScript into a form created with HeyForm. This script would then execute when a team owner reviews the form, potentially allowing the attacker to take over the owner's account by escalating their own privileges.

  • Low-privileged user access required.
  • Malicious script injected into form.
  • Account takeover via privilege escalation.

Live Threat

Current exploitation, exposure, and threat context

A stored cross-site scripting vulnerability in HeyForm's form builder could allow a low-privileged team member to inject malicious JavaScript. This script would execute when a team owner views the form, potentially leading to account takeover through privilege escalation when supported by the advisory.

  • Team owner accounts at risk.
  • Malicious script execution via form viewing.
  • Complete account takeover possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners responsible for HeyForm deployments must first confirm where this open-source form builder exists within their environment, verify its reachability and criticality, and identify the accountable parties before planning remediation. Coordination with the vendor or an internal platform team may be necessary to understand the available patches or mitigation strategies and schedule necessary updates during approved maintenance windows.

  • Application owners should own this issue.
  • Verify HeyForm reachability and criticality first.
  • Plan remediation and coordinate vendor updates.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is HeyForm?

HeyForm is an open-source tool designed for building web-based forms. It allows teams to create, manage, and collect data through customizable interfaces. Because it functions as a centralized data collection point, it is often hosted on web servers where multiple team members interact with form configurations and user-submitted data.

How does CVE-2026-35198 affect the application?

This vulnerability is a Stored Cross-Site Scripting (XSS) issue. In this class of weakness, an attacker saves malicious JavaScript directly into the application's database. When a target, such as an account owner, loads the compromised form, the browser executes the script. This can lead to account takeover, as the script may perform actions on behalf of the owner, effectively escalating the attacker's privileges.

Does this vulnerability trigger if a user simply visits a public form?

No. The vulnerability specifically targets the form management interface. The trigger requires a low-privileged team member to inject malicious code and, crucially, a team owner to view that specific form within the administrative dashboard. It is not triggered by standard public users interacting with the finished forms published on the web.

Is my HeyForm instance at risk?

Halo Surface Signal indicates that HeyForm is typically deployed as a web-facing service, which generally increases accessibility. You are at higher risk if your instance is internet-facing or accessible to a broad range of team members with varying access levels. Organizations should evaluate if their deployment allows internal or external users to reach the form builder's administrative features.

How do I secure my environment against this threat?

The primary step is to update HeyForm to version 3.0.0-rc.7 or later, which contains the official patch for this vulnerability. Before applying the update, identify where HeyForm is deployed in your environment, determine if it is reachable, and coordinate with your internal teams or platform owners to schedule the upgrade during a maintenance window.

References