Skip to content

[Snyk] Security upgrade Umbraco.Cms from 13.12.1 to 14.0.0 - #245

Closed
jcdc-bot wants to merge 1 commit into
dev/v13from
snyk-fix-b5b8487b70c041cf752a2f4ea5a27f3d
Closed

jcdc-bot wants to merge 1 commit into
dev/v13from
snyk-fix-b5b8487b70c041cf752a2f4ea5a27f3d

Conversation

@jcdc-bot

@jcdc-bot jcdc-bot commented Jul 5, 2026

Copy link
Copy Markdown
Collaborator

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the nuget dependencies of this project.

Snyk changed the following file(s):

  • src/TestSite.13/TestSite.13.csproj

Vulnerabilities that will be fixed with an upgrade:

Issue
high severity Directory Traversal
SNYK-DOTNET-LUCENENETREPLICATOR-17816708
high severity Directory Traversal
SNYK-DOTNET-LUCENENETREPLICATOR-17816710

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
馃 View latest project report
馃摐 Customise PR templates
馃洜 Adjust project settings
馃摎 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

馃 Directory Traversal

@jcdc-bot

jcdc-bot commented Jul 5, 2026

Copy link
Copy Markdown
Collaborator Author

Merge Risk: High

The upgrade from Umbraco CMS v13 to v14 is a major version with extensive and significant breaking changes. This is not a routine update and requires substantial planning, code refactoring, and potential content migration.

Key Breaking Changes:

  • Complete Backoffice Rebuild: The backoffice UI has been entirely rebuilt, moving from AngularJS to a modern stack (Web Components, TypeScript). All custom property editors, dashboards, and other backoffice extensions built for v13 and earlier are incompatible and must be rewritten using the new Extension API.

  • Macros Completely Removed: The Macro feature has been entirely removed in v14. Any site functionality or content relying on macros will break. A migration strategy is required to convert existing macros to alternatives like Block List or Block Grid components.

  • Removal of Deprecated Features: Legacy property editors like 'Grid Layout' and 'Nested Content' have been removed. Content using these must be migrated to the more modern Block Grid and Block List editors.

  • API and Code-level Changes:

    • There are significant changes to backend APIs, including the notification handling API for events.
    • A new headless-capable Management API has been introduced, which may affect existing integrations.
    • The client-side asset manager 'Smidge' has been removed, requiring changes to how frontend assets are handled in views.
  • .NET Framework Update: Umbraco 14 requires .NET 8.

Recommendation:
This upgrade should be treated as a major project. Do not merge this change without a thorough analysis of the existing implementation. A detailed migration plan must be developed to address custom code, macros, and deprecated data types. Allocate significant time for development, refactoring, and testing.

Source: Umbraco 14 Release Information, Breaking Changes Overview

Notice 馃: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@github-actions
github-actions Bot requested a review from jcdcdev July 5, 2026 23:23
@jcdc-bot

jcdc-bot commented Jul 5, 2026

Copy link
Copy Markdown
Collaborator Author

鈿狅笍 Snyk checks are incomplete.

Status Scan Engine Critical High Medium Low Total (0)
鈿狅笍 Open Source Security 0 0 0 0 See details

馃捇 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@jcdcdev jcdcdev closed this Jul 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants