How severe is CVE-2013-7082?

No CVSS score has been assigned to CVE-2013-7082 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-7082?

CVE-2013-7082 affects the following packages: neos/flow (Packagist), neos/flow (Packagist), typo3/flow (Packagist), typo3/flow (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2013-7082?

Update neos/flow to 1.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-7082 is resolved across your whole dependency graph.

How do I detect CVE-2013-7082 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neos/flow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-7082 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2013-7082 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-7082 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-7082?

CVE-2013-7082 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 68th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-7082?

CVE-2013-7082 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2013-7082 published, and has it been updated?

CVE-2013-7082 was published on May 17, 2022 and was last updated on December 3, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2013-7082: flow XSS — Fixed in 1.1.1

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

🐘neos/flow🐘neos/flow🐘typo3/flow🐘typo3/flow

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Cross-site scripting (XSS) vulnerability in the errorAction method in the ActionController base class in TYPO3 Flow (formerly FLOW3) 1.1.x before 1.1.1 and 2.0.x before 2.0.1 allows remote attackers to inject arbitrary web script or HTML via unspecified input, which is returned in an error message.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`neos/flow`	≥ 1.1.0&&< 1.1.1	1.1.1`composer require neos/flow:^1.1.1`
🐘Packagist	`neos/flow`	≥ 2.0.0&&< 2.0.1	2.0.1`composer require neos/flow:^2.0.1`
🐘Packagist	`typo3/flow`	≥ 1.1.0&&< 1.1.1	1.1.1`composer require typo3/flow:^1.1.1`
🐘Packagist	`typo3/flow`	≥ 2.0.0&&< 2.0.1	2.0.1`composer require typo3/flow:^2.0.1`

Affected Products

1 product · 2 configurations

Application

flowtypo3

2 versions

1.1.02.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neos/flow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update neos/flow to 1.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-7082 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Cross-site scripting (XSS) vulnerability in the errorAction method in the ActionController base class in TYPO3 Flow (formerly FLOW3) 1.1.x before 1.1.1 and 2.0.x before 2.0.1 allows remote attackers to inject arbitrary web script or HTML via unspecified input, which is returned in an error message.

O3 Security · Impact-Aware SCA

Is CVE-2013-7082 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2013-7082 — flow