Umbraco.Forms
Affected
- introduced
7.0.0, fixed13.4.2(ecosystem)
Fixed versions
13.4.2
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2025-47280
Umbraco.Forms has HTML injection vulnerability in 'Send email' workflow
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):
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>();
}Low Basis: The source's own band: LOW
7.0.0, fixed 13.4.2 (ecosystem)13.4.2
The export has no generic command for this ecosystem.
7.0.0, last affected 8.13.16 (ecosystem)None listed
No fixed version is listed.
14.0.0, fixed 15.1.2 (ecosystem)15.1.2
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0