dbcve.org
FormieApplication · Verbb

CVE-2025-32426

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-11
Fix available
A fix is available. Upgrade to 2.1.44 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Formie is a Craft CMS plugin for creating forms. Prior to version 2.1.44, it is possible to inject malicious code into the HTML content of an email notification, which is then rendered on the preview. There is no issue when rendering the email via normal means (a delivered email). This would require access to the form's email notification settings. This has been fixed in Formie 2.1.44.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stored HTML injection (XSS) in Formie plugin's email notification preview. An authenticated user with access to form email notification settings can inject malicious HTML/JavaScript that renders only in the admin preview panel, not in actual delivered emails. Fixed in version 2.1.44.

MitigationUpdate Formie plugin to version 2.1.44 or later. Verify form functionality after update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FormieApplication
Affected:< 2.1.44

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Formie plugin version
    Locate the Formie plugin in your Craft CMS installation and inspect its version metadata (typically in composer.json, plugin.json, or the plugins admin panel under Settings > Plugins)
    Affected if Installed version is below 2.1.44
  2. Identify users with email notification access
    Review user permissions and form settings to determine which authenticated users have access to form email notification configuration (typically found under Formie > Forms > [form] > Notifications)
    Affected if Any authenticated user with low privileges or compromised credentials can access email notification settings
  3. Inspect email notification preview configurations
    Examine stored email notification records in the database or via Formie admin interface, specifically looking at the preview/render settings for each notification
    Affected if HTML or JavaScript content appears in notification preview fields that was not intentionally authored by an administrator
  4. Review admin activity logs for notification edits
    Check Craft CMS logs and Formie audit logs for recent modifications to email notification settings, particularly unexpected or malicious-looking HTML content
    Affected if Recent notification edits contain suspicious HTML/JS payloads that were not from legitimate admin sessions

User is affected if Formie plugin version is below 2.1.44 and email notification settings contain unauthorized HTML/JavaScript in preview configurations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.44 or later
Fixed in 2.1.44
Interim mitigation

Update Formie plugin to version 2.1.44 or later. Verify form functionality after update.

Recommended fix High confidence

Formie 2.1.44

  1. 1. Backup your Craft CMS site and database before performing any updates.
  2. 2. Navigate to the Craft CMS control panel.
  3. 3. Go to Settings → Plugins.
  4. 4. Locate Formie in the list of installed plugins.
  5. 5. Click the update button/check for updates to see if version 2.1.44 is available.
  6. 6. If available, click to update Formie to version 2.1.44.
  7. 7. Alternatively, if using Composer, run: composer require verbb/formie:^2.1.44 to update the plugin.
  8. 8. After updating, clear any caches to ensure the new version is fully applied.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Formie Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32426 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32426 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data