Is @umbraco-cms/backoffice 14.1 vulnerable?

npm · 3 releases from 14.1.0 to 14.1.2 · latest @umbraco-cms/backoffice is 17.8.2 · checked 20 Nov 2026

Yes: 2 known advisories

Yes. @umbraco-cms/backoffice 14.1.2, the last 14.1 release, is affected by 2 known security advisories (2 medium), including CVE-2025-24012, CVE-2024-47819. Upgrade to 14.3.2 or later to fix all of them.

Upgrade with:npm install @umbraco-cms/backoffice@14.3.2

Is your project on an affected @umbraco-cms/backoffice?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting @umbraco-cms/backoffice 14.1.2

  • MediumCVE-2025-24012GHSA-wv8v-rmw2-25wc21 Jan 2025

    XSS/HTML Injection Vulnerability in Umbraco Backoffice Components

    Affected
    >=14.0.0 <14.3.2 · >=15.0.0 <15.1.2
    Fixed in
    14.3.2, 15.1.2
  • MediumCVE-2024-47819GHSA-c5g6-6xf7-qxp322 Oct 2024

    Umbraco CMS vulnerable to stored Cross-site Scripting in the "dictionary name" on Dictionary section

    Affected
    >=14.0.0 <14.3.1
    Fixed in
    14.3.1

Every @umbraco-cms/backoffice 14.1.x release

Affected: 14.1.0 to 14.1.2. Latest @umbraco-cms/backoffice: 17.8.2.

VersionKnown advisories
@umbraco-cms/backoffice 14.1.2CVE-2025-24012, CVE-2024-47819
@umbraco-cms/backoffice 14.1.1CVE-2025-24012, CVE-2024-47819
@umbraco-cms/backoffice 14.1.0CVE-2025-24012, CVE-2024-47819

Which of your client projects are still on @umbraco-cms/backoffice 14.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact @umbraco-cms/backoffice version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other @umbraco-cms/backoffice versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.