dbcve.org
Umbraco FormsApplication · Umbraco

CVE-2024-35239

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-28
Fix available
A fix is available. Upgrade to 8.13.13 / 10.5.3 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
Umbraco Commerce is an open source dotnet web forms solution. In affected versions an authenticated user that has access to edit Forms may inject unsafe code into Forms components. This issue can be mitigated by configuring TitleAndDescription:AllowUnsafeHtmlRendering after upgrading to one of the patched versions (13.0.1, 12.2.2, 10.5.3, 8.13.13).

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

Authenticated users with Forms edit access can inject unsafe HTML/script code into Forms components in Umbraco Commerce, representing a stored XSS vulnerability. The vulnerability stems from insufficient sanitization of user-supplied content in Title and Description fields. Patched versions 13.0.1, 12.2.2, 10.5.3, and 8.13.13 address this, with additional mitigation available via the TitleAndDescription:AllowUnsafeHtmlRendering configuration setting.

MitigationUpgrade to a patched version (13.0.1, 12.2.2, 10.5.3, or 8.13.13) and configure TitleAndDescription:AllowUnsafeHtmlRendering to disable unsafe HTML rendering in Forms components.

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
Umbraco FormsApplication
Affected:< 8.13.13>= 9.0.0, < 10.5.3>= 11.0.0, < 12.2.2>= 13.0.0, < 13.0.1

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. Determine installed Umbraco Forms version
    Locate the Umbraco Forms package version from the solution's packages.config, .csproj references, or the installed packages list in the Umbraco backoffice under the 'Packages' section
    Affected if The installed version falls within any of these ranges: < 8.13.13; >= 9.0.0 and < 10.5.3; >= 11.0.0 and < 12.2.2; >= 13.0.0 and < 13.0.1
  2. Locate the Forms configuration file
    Find the Umbraco Forms configuration file, typically named Umbraco.Forms.config or found within the App_Config/UmbracoForms folder in the application root
    Affected if The configuration file exists and contains the TitleAndDescription section
  3. Check AllowUnsafeHtmlRendering setting
    Inspect the configuration for the TitleAndDescription:AllowUnsafeHtmlRendering setting; if absent, the default behavior applies (unsafe HTML is rendered)
    Affected if The setting is either absent (defaulting to unsafe rendering) or set to true/enabled, meaning HTML/script in Title and Description fields is rendered without sanitization

You are affected if your Umbraco Forms version is within the vulnerable ranges AND users with Forms edit access can create or modify Forms with Title or Description fields containing unsanitized HTML or script content.

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 8.13.13 / 10.5.3 / 12.2.2 or later
Fixed in 8.13.1310.5.312.2.2
Interim mitigation

Upgrade to a patched version (13.0.1, 12.2.2, 10.5.3, or 8.13.13) and configure TitleAndDescription:AllowUnsafeHtmlRendering to disable unsafe HTML rendering in Forms components.

Recommended fix High confidence

Umbraco Forms 8.13.13, 10.5.3, 12.2.2, or 13.0.1 depending on your current major version branch

  1. 1. Identify your current Umbraco Forms version by checking the installed package version in your project or Umbraco backoffice.
  2. 2. Determine which upgrade path applies based on your current major version: for versions < 8.x upgrade to 8.13.13; for 9.x-10.x upgrade to 10.5.3; for 11.x upgrade to 12.2.2; for 13.x upgrade to 13.0.1.
  3. 3. Update the Umbraco Forms NuGet package in your project to the appropriate fixed version, or use the Umbraco backoffice package manager to install the patched version.
  4. 4. Test the upgrade in a non-production environment first to verify compatibility with your custom code and other installed packages.
  5. 5. After upgrading, to further mitigate XSS risk, configure the TitleAndDescription:AllowUnsafeHtmlRendering setting in your configuration files (appsettings.json or equivalent) to disable unsafe HTML rendering if not already disabled by default.
Caveat Review release notes for your target version as minor/patch releases typically maintain backward compatibility but always test in staging first

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

Fix this in Umbraco Forms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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