MediumGHSA-43cf-7f3h-38rg

Privilege Escalation in TYPO3 Neos

Published 17 May 2024 · Updated 17 May 2024

Is your project on an affected neos/neos?

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

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

Affected packages

neos/neosComposer
Affected
>=1.1.0 <1.1.3
Fixed in
1.1.3
Update to the fixed version for your release line, for example:composer require neos/neos:^1.1.3
neos/neosComposer
Affected
>=1.2.0 <1.2.3
Fixed in
1.2.3
Update to the fixed version for your release line, for example:composer require neos/neos:^1.2.3

Details

It has been discovered that TYPO3 Neos is vulnerable to Privilege Escalation. Logged in editors could access, create and modify content nodes that exist in the workspace of other editors.

Is GHSA-43cf-7f3h-38rg in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected neos/neos, and gives you the command that fixes it.

More advisories for neos/neos

  • HighGHSA-6cj3-rc4p-f38fCross-site Scripting vulnerabilities in Neos · 17 May 2024
  • HighGHSA-3c5g-73f7-grvmNeos Information Disclosure Security Note · 17 May 2024
  • MediumCVE-2022-30429Neos CMS vulnerable to XSS in various backend modules · 3 Jun 2022
  • MediumGHSA-jfxf-4frr-9j3qXSS in various backend modules due to (un)escaping in JS notification module · 25 May 2022
neos/neos security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.