CVE-2013-7082: TYPO3 Flow Cross-site scripting (XSS) vulnerability

CVE-2013-7082 · Severity: info · Published 2022-05-17

TYPO3 Flow Cross-site scripting (XSS) vulnerability

Technologies: neos/flow (Packagist), typo3/flow (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2013-7082 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2013-7082 being exploited in the wild.
How severe is CVE-2013-7082?
Informational severity, published 17 May 2022.
Which products and versions are affected?
neos/flow (Packagist) ECOSYSTEM:introduced=1.1.0,fixed=1.1.1; typo3/flow (Packagist) ECOSYSTEM:introduced=1.1.0,fixed=1.1.1.
Is there a fix for CVE-2013-7082?
Yes. neos/flow (Packagist): upgrade to 1.1.1 or later; typo3/flow (Packagist): upgrade to 1.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2013-7082?
Check whether you run neos/flow (Packagist) or typo3/flow (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/flow (Packagist): upgrade to 1.1.1 or later
    composer require neos/flow:^1.1.1
  • typo3/flow (Packagist): upgrade to 1.1.1 or later
    composer require typo3/flow:^1.1.1

Affected products

  • neos/flow (Packagist) ECOSYSTEM:introduced=1.1.0,fixed=1.1.1
  • typo3/flow (Packagist) ECOSYSTEM:introduced=1.1.0,fixed=1.1.1

Identifiers

  • CVE-2013-7082
  • GHSA-vc74-c4m6-9979

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