CVE-2010-4509: Critical severity Sixapart Movabletype vulnerability
Published Dec 9, 2010
·Updated
Multiple unspecified vulnerabilities in Movable Type 4.x before 4.35 and 5.x before 5.04 have unknown impact and attack vectors related to the (1) mt:AssetProperty and (2) mt:EntryFlag tags.
Affected Software
17 affected components
Sixapart Movabletype=4.33
Sixapart Movabletype=4.34
Sixapart Movabletype=4.0
Sixapart Movabletype=4.1
Sixapart Movabletype=4.32
Sixapart Movabletype=4.2
Sixapart Movabletype=4.26
Sixapart Movabletype=4.23
Sixapart Movabletype=4.25
Sixapart Movabletype=5.02
Sixapart Movabletype=4.3
Sixapart Movabletype=4.31
Sixapart Movabletype=5.01
Sixapart Movabletype=5.031
Sixapart Movabletype=4.261
Sixapart Movabletype=5.0-rc2
Sixapart Movabletype=5.03
Event History
Dec 9, 2010
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2010-4509?
The severity of CVE-2010-4509 is currently unknown due to unspecified vulnerabilities.
2
How do I fix CVE-2010-4509?
To fix CVE-2010-4509, upgrade Movable Type to version 4.35 or 5.04 or later.
3
Which versions of Movable Type are affected by CVE-2010-4509?
CVE-2010-4509 affects Movable Type versions 4.x before 4.35 and 5.x before 5.04.
4
What are the attack vectors for CVE-2010-4509?
The attack vectors for CVE-2010-4509 are currently unspecified and have unknown impact.
5
Are there any workarounds for CVE-2010-4509?
There are no specific workarounds for CVE-2010-4509; upgrading to a secure version is recommended.