CVE-2009-3630: Medium severity typo3 vulnerability

Published Nov 2, 2009
·
Updated

The Backend subcomponent in TYPO3 4.0.13 and earlier, 4.1.x before 4.1.13, 4.2.x before 4.2.10, and 4.3.x before 4.3beta2 allows remote authenticated users to place arbitrary web sites in TYPO3 backend framesets via crafted parameters, related to a "frame hijacking" issue.

Affected Software

63 affected componentsFixes available
composer/typo3/cms-backend>=4.3alpha1<4.3beta2
4.3beta2
composer/typo3/cms-backend>=4.2.0<4.2.10
4.2.10
composer/typo3/cms-backend>=4.1.0<4.1.13
4.1.13
composer/typo3/cms-backend<=4.0.13
Typo3 TYPO3<=4.0.12
Typo3 TYPO3=0.1.2
Typo3 TYPO3=1.0.14
Typo3 TYPO3=1.1
Typo3 TYPO3=1.1.1
Typo3 TYPO3=1.1.09
Typo3 TYPO3=1.1.10
Typo3 TYPO3=1.2.0
Typo3 TYPO3=1.3.0
Typo3 TYPO3=1.3.2
Typo3 TYPO3=3.0
Typo3 TYPO3=3.3.x
Typo3 TYPO3=3.5
Typo3 TYPO3=3.5.x
Typo3 TYPO3=3.6.x
Typo3 TYPO3=3.7.0
Typo3 TYPO3=3.7.1
Typo3 TYPO3=3.7.x
Typo3 TYPO3=3.8
Typo3 TYPO3=3.8.x
Typo3 TYPO3=4.0
Typo3 TYPO3=4.0.1
Typo3 TYPO3=4.0.2
Typo3 TYPO3=4.0.3
Typo3 TYPO3=4.0.4
Typo3 TYPO3=4.0.5
Typo3 TYPO3=4.0.6
Typo3 TYPO3=4.0.7
Typo3 TYPO3=4.0.8
Typo3 TYPO3=4.0.9
Typo3 TYPO3=4.0.10
Typo3 TYPO3=4.0.11
Typo3 TYPO3=4.1.0
Typo3 TYPO3=4.1.0-beta1
Typo3 TYPO3=4.1.0-rc1
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.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.3
Typo3 TYPO3=4.3-alpha1

Event History

Nov 2, 2009
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
May 2, 2022
Advisory Published
via GitHub·03:46 AM

Frequently Asked Questions

1

What is the severity of CVE-2009-3630?

CVE-2009-3630 is classified as a vulnerability that allows remote authenticated users to perform frame hijacking within the TYPO3 backend.

2

How do I fix CVE-2009-3630?

To fix CVE-2009-3630, update TYPO3 to version 4.3beta2 or later, 4.2.10, or 4.1.13.

3

Which versions of TYPO3 are affected by CVE-2009-3630?

CVE-2009-3630 affects TYPO3 versions up to and including 4.3beta1, as well as versions 4.0.13 and earlier.

4

Can CVE-2009-3630 be exploited by unauthenticated users?

No, CVE-2009-3630 requires authentication, thus only remote authenticated users can exploit this vulnerability.

5

What type of attack does CVE-2009-3630 facilitate?

CVE-2009-3630 facilitates a frame hijacking attack by allowing malicious framed content to be displayed within the TYPO3 backend.

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