dbcve.org
Umbraco FormsApplication · Umbraco

CVE-2025-47280

MEDIUM · 6.1 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 13.4.2 / 15.1.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Public exploit Remotely reachable No privileges

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
Umbraco Forms is a form builder that integrates with the Umbraco content management system. Starting in the 7.x branch and prior to versions 13.4.2 and 15.1.2, the 'Send email' workflow does not HTML encode the user-provided field values in the sent email message, making any form with this workflow configured vulnerable, as it allows sending the message from a trusted system and address, potentially bypassing spam and email client security systems. This issue affects all (supported) versions Umbraco Forms and is patched in 13.4.2 and 15.1.2. Unpatched or unsupported versions can workaround this issue by using the `Send email with template (Razor)` workflow instead or writing a custom workflow type. To avoid accidentally using the vulnerable workflow again, the `SendEmail` workflow type can be removed using a composer available in the GitHub Security Advisory for this vulnerability.

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

A detailed technical summary for this CVE is being prepared.

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
Umbraco FormsApplication
Affected:>= 7.0.0, < 13.4.2>= 14.0.0, < 15.1.2

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 13.4.2 / 15.1.2 or later
Fixed in 13.4.215.1.2
Recommended fix High confidence

Umbraco Forms 13.4.2 (for 13.x branch) or 15.1.2 (for 14.x/15.x branch)

  1. 1. Identify the current installed version of Umbraco Forms by checking the package reference in the project (e.g., in .csproj, packages.config, or NuGet package manager)
  2. 2. If running on the 13.x branch (Umbraco 13.x), upgrade to Umbraco Forms version 13.4.2 or later using NuGet: `Update-Package Umbraco.Forms` or `dotnet add package Umbraco.Forms --version 13.4.2`
  3. 3. If running on the 14.x or 15.x branch, upgrade to Umbraco Forms version 15.1.2 or later using NuGet: `Update-Package Umbraco.Forms` or `dotnet add package Umbraco.Forms --version 15.1.2`
  4. 4. Rebuild and redeploy the application after upgrading the package
  5. 5. Verify the upgrade was successful by checking the installed version in the Umbraco backoffice under the 'Umbraco Forms' section
  6. 6. Test the 'Send email' workflow with HTML-sensitive input (e.g., `<script>alert(1)</script>`) in a form field to confirm the vulnerability is patched and the input is properly encoded in outgoing emails
Caveat Upgrading between major version branches (e.g., from 12.x to 13.x) may introduce breaking changes in Umbraco Forms; review the Umbraco migration guides and release notes before upgrading

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47280 — 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-47280 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