Skip to content

← Public intelligence

NuGet package

umbraco.cms.api.management

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.3NuGetPublished

    Umbraco Allows Improper API Access Control to Low-Privilege Users to Data Type Functionality

    CVE-2025-27601 · GHSA-6ffg-mjg7-585x

    Affected
    • NuGet umbraco.cms.api.management >= 15.0.0-rc1, <= 15.2.2; <= 14.3.2
    Fixed in
    15.2.314.3.3· Vendor fix available
    Issue
    Impact An improper API access control issue has been identified, allowing low-privilege, authenticated users to create and update data type information that should be restricted to users with access to the settings section. Patches Will be patched in 14.3.3 and 15.2.3. Workarounds None available.

    Recommended action: Upgrade to 15.2.3 or 14.3.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 5.3NuGetPublished

    Umbraco CMS vulnerable to Generation of Error Message Containing Sensitive Information

    CVE-2024-43376 · GHSA-77gj-crhp-3gvx

    Affected
    • NuGet umbraco.cms.api.management >= 14.0.0, < 14.1.2
    Fixed in
    14.1.2· Vendor fix available
    Issue
    Impact Some endpoints in the Management API can return stack trace information, even when Umbraco is not in debug mode. Explanation of the vulnerability Management API endpoints leaked stack traces in case of Internal server errors, no matter if the debug setting was disabled. E.g. when paging with negative numbers in some apis

    Recommended action: Upgrade to 14.1.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →