CVE-2022-30429: Neos CMS vulnerable to XSS in various backend modules

CVE-2022-30429 · Severity: low · CVSS 3.1 · Published 2022-06-03

Neos CMS vulnerable to XSS in various backend modules

Technologies: neos/neos (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2022-30429 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-30429 being exploited in the wild.
How severe is CVE-2022-30429?
Low severity, with a CVSS score of 3.1, published 3 June 2022.
Which products and versions are affected?
neos/neos (Packagist) ECOSYSTEM:introduced=3.3.0,fixed=4.4.0.
Is there a fix for CVE-2022-30429?
Yes. neos/neos (Packagist): upgrade to 4.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-30429?
Check whether you run neos/neos (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • neos/neos (Packagist): upgrade to 4.4.0 or later
    composer require neos/neos:^4.4.0

Affected products

  • neos/neos (Packagist) ECOSYSTEM:introduced=3.3.0,fixed=4.4.0

Identifiers

  • CVE-2022-30429
  • GHSA-7m9h-v68w-pfw3

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.