External risk intelligence

Formie Craft CMS Plugin Twig Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-45697

The vulnerability exists in a web form plugin for a CMS. Web forms are designed to be public-facing and are intended to be accessed and submitted by unauthenticated users over the internet as part of normal site operations.

Code Injection

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability exists in the Formie plugin for Craft CMS, allowing unauthenticated users to submit malicious input that could lead to a severe compromise of the website. This issue arises from the plugin's handling of specially crafted values in hidden form fields, which can be evaluated as code.

  • Unauthenticated users can submit malicious input.
  • It could compromise the entire website.
  • Confirm if Formie is used and verify exposure.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by submitting specially crafted data to a publicly accessible web form. This data is processed by the Formie plugin, which incorrectly evaluates user-supplied values as Twig code. This could allow an attacker to execute arbitrary code or gain unauthorized access to sensitive information on the Craft CMS site.

  • Entry condition: Publicly accessible web form.
  • Trigger point: Submitting crafted hidden field values.
  • Resulting risk: Serious site compromise.

Live Threat

Current exploitation, exposure, and threat context

Unauthenticated users could submit specially crafted values to hidden form fields that are evaluated as Twig code, potentially leading to a serious compromise of the Craft CMS site. This compromise depends on the specific template and sandbox configurations of the affected site.

  • Site's template and configuration data.
  • Malicious input submitted via public forms.
  • Full site compromise, including data exposure.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and infrastructure teams are likely responsible for addressing this vulnerability in the Formie Craft CMS plugin. The first practical step is to identify all instances of the affected plugin, determine their reachability and business criticality, and then engage the accountable owners to plan remediation, which may involve coordinating with vendors and scheduling maintenance windows.

  • Identify affected sites and owners.
  • Verify plugin reachability and criticality.
  • Plan coordinated vendor-supported 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 Formie?

Formie is a plugin for Craft CMS designed to help developers build and manage custom web forms. It is widely used by site administrators to collect user data, handle submissions, and integrate form functionality directly into their content management workflow.

What does CVE-2026-45697 mean?

This CVE describes a security weakness known as Improper Neutralization of Special Elements, or Code Injection. Specifically, the plugin incorrectly treats user-provided input in hidden form fields as executable Twig template code. This allows an attacker to inject and run unauthorized code on the server hosting the website.

How can an attacker trigger this bug?

An attacker triggers this by submitting specific, malicious data into hidden fields within a Formie form. It is important to note that regular form submissions or using visible fields as intended will not trigger this vulnerability. The flaw specifically relies on the improper evaluation of values within those hidden, custom-default fields.

Why should I care if my forms are internet-facing?

According to Halo Surface Signal, this vulnerability is particularly relevant because web forms are inherently designed to be public-facing. Since your forms are intended for use by unauthenticated users over the internet, an attacker can interact with the vulnerable plugin without needing any special access or prior authentication to your CMS.

How do I fix the Formie vulnerability?

The first step is to locate every instance of Formie running in your environment. Once identified, you should prioritize updating the plugin to version 2.2.20 or 3.1.24, which contain the necessary security patches. Coordination with your web team is recommended to verify these updates and ensure they are applied successfully without disrupting site operations.

References