CVE-2010-3659: XSS

Published Oct 20, 2017
·
Updated

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 Software

37 affected componentsFixes available
composer/typo3/cms-backend>=4.4.0<4.4.1
4.4.1
composer/typo3/cms-backend>=4.3.0<4.3.4
4.3.4
composer/typo3/cms-backend>=4.2.0<4.2.13
4.2.13
composer/typo3/cms-backend>=4.1.0<4.1.14
4.1.14
debian/typo3-src
Typo3 TYPO3=4.1.0
Typo3 TYPO3=4.1.1
Typo3 TYPO3=4.1.2
Typo3 TYPO3=4.1.3
Typo3 TYPO3=4.1.4
Typo3 TYPO3=4.1.5
Typo3 TYPO3=4.1.6
Typo3 TYPO3=4.1.7
Typo3 TYPO3=4.1.8
Typo3 TYPO3=4.1.9
Typo3 TYPO3=4.1.10
Typo3 TYPO3=4.1.11
Typo3 TYPO3=4.1.12
Typo3 TYPO3=4.1.13
Typo3 TYPO3=4.2.0
Typo3 TYPO3=4.2.1
Typo3 TYPO3=4.2.2
Typo3 TYPO3=4.2.3
Typo3 TYPO3=4.2.4
Typo3 TYPO3=4.2.5
Typo3 TYPO3=4.2.6
Typo3 TYPO3=4.2.7
Typo3 TYPO3=4.2.8
Typo3 TYPO3=4.2.9
Typo3 TYPO3=4.2.10
Typo3 TYPO3=4.2.11
Typo3 TYPO3=4.2.12
Typo3 TYPO3=4.3.0
Typo3 TYPO3=4.3.1
Typo3 TYPO3=4.3.2
Typo3 TYPO3=4.3.3
Typo3 TYPO3=4.4.0

Event History

Oct 20, 2017
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
May 17, 2022
Advisory Published
via GitHub·12:26 AM

Frequently Asked Questions

1

What is the severity of CVE-2010-3659?

CVE-2010-3659 is classified as having moderate severity due to its multiple cross-site scripting (XSS) vulnerabilities.

2

How do I fix CVE-2010-3659?

You can resolve CVE-2010-3659 by upgrading TYPO3 to versions 4.1.14, 4.2.13, 4.3.4, or 4.4.1 or higher.

3

What systems are affected by CVE-2010-3659?

CVE-2010-3659 affects TYPO3 CMS versions 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.

4

Can CVE-2010-3659 be exploited remotely?

Yes, CVE-2010-3659 can be exploited remotely by authenticated backend users to inject arbitrary web scripts or HTML.

5

What measures can I take to mitigate CVE-2010-3659?

To mitigate CVE-2010-3659, users should apply the latest security patches and limit backend access to trusted users only.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203