@umbraco-cms/backoffice vulnerabilities
This package contains the types for the Umbraco Backoffice.
- Registry
- npm
- Latest
- 17.8.2
- License
- MIT
2 known advisories
The latest version, 17.8.2, is not affected by any of them. Projects on older versions may be.
npm install @umbraco-cms/backoffice@17.8.2Is your project on an affected @umbraco-cms/backoffice?
Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for @umbraco-cms/backoffice
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
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
Is your @umbraco-cms/backoffice version vulnerable?
- @umbraco-cms/backoffice 18.3No known advisories in 18.3.2
- @umbraco-cms/backoffice 18.2No known advisories in 18.2.2
- @umbraco-cms/backoffice 18.1No known advisories in 18.1.1
- @umbraco-cms/backoffice 18.0No known advisories in 18.0.2
- @umbraco-cms/backoffice 17.8No known advisories in 17.8.2
- @umbraco-cms/backoffice 17.7No known advisories in 17.7.2
- @umbraco-cms/backoffice 17.6No known advisories in 17.6.2
- @umbraco-cms/backoffice 17.5No known advisories in 17.5.3
- @umbraco-cms/backoffice 17.4No known advisories in 17.4.2
- @umbraco-cms/backoffice 17.3No known advisories in 17.3.5
- @umbraco-cms/backoffice 16.5No known advisories in 16.5.1
- @umbraco-cms/backoffice 16.4No known advisories in 16.4.1
- @umbraco-cms/backoffice 16.3No known advisories in 16.3.4
- @umbraco-cms/backoffice 16.2No known advisories in 16.2.0
- @umbraco-cms/backoffice 16.1No known advisories in 16.1.1
- @umbraco-cms/backoffice 16.0No known advisories in 16.0.0
Which of your client projects still run an old @umbraco-cms/backoffice?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.