CVE-2026-45697: Formie: Pre-authenticated server-side template injection in Hidden fields
Formie is a Craft CMS plugin for creating forms. Prior to 2.2.20 and 3.1.24, unauthenticated users could submit crafted values into Hidden fields (with Default value → Custom) that were evaluated as Twig during submission handling, which could lead to serious compromise of the Craft site (depending on template/sandbox behavior). This vulnerability is fixed in 2.2.20 and 3.1.24.
Security readout for executives and security teams
Plain-English summary
This flaw lets an unauthenticated visitor submit specially crafted Hidden field values in Formie that may be evaluated as Twig templates. On affected Craft CMS sites, that can turn a normal public form into a path to serious site compromise. The vendor fixed it in Formie 2.2.20 and 3.1.24.
Executive priority
Treat this as urgent for any public Craft CMS site using Formie. The combination of pre-authentication reachability, critical CVSS score, and possible full site compromise makes patching a near-term priority even without confirmed exploitation.
Technical view
CVE-2026-45697 is a pre-authenticated server-side template injection in verbb Formie Hidden fields configured with Default value set to Custom. Affected versions are before 2.2.20 and 3.0.0-beta.1 through before 3.1.24. CVSS 3.1 is 9.8, with network access, low complexity, no privileges, and no user interaction.
Likely exposure
Internet-facing Craft CMS sites using vulnerable Formie versions are the main concern, especially where public forms accept unauthenticated submissions and use Hidden fields with Custom default values.
Exploitation context
The provided sources do not state active exploitation, and the CVE is not marked KEV. Exploitability is still serious because the issue is pre-authenticated, network-reachable, low complexity, and may affect confidentiality, integrity, and availability depending on Twig template and sandbox behavior.
Researcher notes
The source bundle maps this to CWE-1336, CWE-693, and CWE-94. Evidence supports a Twig evaluation flaw during submission handling, but does not provide safe detection signatures, IOCs, exploit prevalence, or detailed environmental constraints beyond template and sandbox behavior.
Mitigation direction
Upgrade Formie 2.x deployments to 2.2.20 or later.
Upgrade Formie 3.x deployments to 3.1.24 or later.
Prioritize public Craft CMS sites with unauthenticated form submissions.
Review vendor guidance before relying on temporary workarounds.
If upgrade is delayed, consider disabling affected public forms temporarily.
Validation and detection
Inventory Craft CMS sites using the verbb Formie plugin.
Confirm installed Formie versions against the affected ranges.
Review forms for Hidden fields using Custom default values.
Check recent form submissions and logs for suspicious activity; sources provide no IOCs.
Verify the site runs 2.2.20, 3.1.24, or a later fixed release.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1336: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1336 · source CWE mapping
Improper Neutralization of Special Elements Used in a Template Engine
Improper Neutralization of Special Elements Used in a Template Engine represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.