CVE-2025-47280: Umbraco.Forms has HTML injection vulnerability in 'Send email' workflow

Published May 13, 2025
·
Updated

Impact 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).

Patches This issue affects all (supported) versions Umbraco Forms and is patched in 13.4.2 and 15.1.2.

Workarounds 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 the following composer (tested on Umbraco 10, 13, 14 and 15): c# using Umbraco.Cms.Core.Composing; using Umbraco.Forms.Core.Providers.Extensions; using Umbraco.Forms.Core.Providers.WorkflowTypes;

internal sealed class RemoveFormsSendEmailWorkflowTypeComposer : IComposer { public void Compose(IUmbracoBuilder builder) => builder.FormsWorkflows().Exclude<SendEmail>(); }

Other sources

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.

MITRE

Affected Software

6 affected componentsFixes available
Umbraco Umbraco Forms<13.4.2, <15.1.2, >=7.x
nuget/Umbraco.Forms>=14.0.0<15.1.2
15.1.2
nuget/UmbracoForms>=7.0.0<=8.13.16
nuget/Umbraco.Forms>=7.0.0<13.4.2
13.4.2
Umbraco Umbraco Forms>=7.0.0<13.4.2
Umbraco Umbraco Forms>=14.0.0<15.1.2

Event History

May 13, 2025
CVE Published
via MITRE·05:06 PM
Data Sourced
via MITRE·05:06 PM
DescriptionWeakness
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·08:17 PM
Mar 30, 57351
Event
via FIRST·05:00 AM

Frequently Asked Questions

1

What is the severity of CVE-2025-47280?

CVE-2025-47280 is categorized as a medium severity vulnerability due to potential issues with user data handling.

2

How do I fix CVE-2025-47280?

To mitigate CVE-2025-47280, upgrade to Umbraco Forms versions 13.4.2 or 15.1.2 or later.

3

What does CVE-2025-47280 exploit?

CVE-2025-47280 exploits the lack of HTML encoding of user-provided field values in email messages sent by Umbraco Forms.

4

Which versions of Umbraco Forms are affected by CVE-2025-47280?

CVE-2025-47280 affects Umbraco Forms versions from 7.x up to, but not including, 13.4.2 and 15.1.2.

5

What impact does CVE-2025-47280 have on web applications?

CVE-2025-47280 can lead to security issues such as cross-site scripting (XSS) if an attacker submits malicious input.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203