How severe is CVE-2010-3659?

CVE-2010-3659 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2010-3659?

CVE-2010-3659 affects the following packages: typo3/cms-backend (Packagist), typo3/cms-backend (Packagist), typo3/cms-backend (Packagist), typo3/cms-backend (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2010-3659?

Update typo3/cms-backend to 4.1.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-3659 is resolved across your whole dependency graph.

How do I detect CVE-2010-3659 in my Packagist dependencies?

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

How do I mitigate CVE-2010-3659 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-2010-3659 actively exploited in the wild?

No public exploit code has been indexed for CVE-2010-3659 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-2010-3659?

CVE-2010-3659 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th 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-2010-3659?

CVE-2010-3659 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-2010-3659 published, and has it been updated?

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

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2010-3659 — cms-backend

MEDIUM

CVE-2010-3659 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in typo3/cms-backend. A fix is available for typo3/cms-backend — see the affected versions and patch details below.

TYPO3 Cross-site Scripting vulnerability in the extension manager and backend forms

Published

May 17, 2022

Updated

Feb 7, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐘typo3/cms-backend🐘typo3/cms-backend🐘typo3/cms-backend🐘typo3/cms-backend

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

Multiple cross-site scripting (XSS) vulnerabilities in TYPO3 CMS 4.1.x before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4, and 4.4.x before 4.4.1 allow remote authenticated backend users to inject arbitrary web script or HTML via unspecified parameters to the extension manager, or unspecified parameters to unknown backend forms.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-backend`	≥ 4.1.0&&< 4.1.14	4.1.14`composer require typo3/cms-backend:^4.1.14`
🐘Packagist	`typo3/cms-backend`	≥ 4.2.0&&< 4.2.13	4.2.13`composer require typo3/cms-backend:^4.2.13`
🐘Packagist	`typo3/cms-backend`	≥ 4.3.0&&< 4.3.4	4.3.4`composer require typo3/cms-backend:^4.3.4`
🐘Packagist	`typo3/cms-backend`	≥ 4.4.0&&< 4.4.1	4.4.1`composer require typo3/cms-backend:^4.4.1`

Affected Products

1 product · 32 configurations

Application

typo3typo3

32 versions

4.1.04.1.14.1.24.1.34.1.44.1.54.1.64.1.74.1.84.1.94.1.104.1.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-backend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-backend to 4.1.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-3659 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

O3 Security · Impact-Aware SCA

Is CVE-2010-3659 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

May 17, 2022

Last updated

Feb 7, 2024

Identifiers

CVE-2010-3659

References

Advisorynvd.nist.gov · CVE 2010 3659 Websecurity-tracker.debian.org · CVE 2010 3659 Webtypo3.org · typo3 sa 2010 012 Webweb.archive.org Webopenwall.com Webopenwall.com Packagegithub.com · backend

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting typo3/cms-backend are rated as high or higher (top: high).

CVE-2026-19418CVE-2026-47352CVE-2026-47351CVE-2026-6553CVE-2025-59020CVE-2025-59017CVE-2025-59019CVE-2025-59014

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 7, 2024