CVE-2010-4511: Critical severity Sixapart Movabletype vulnerability
Published Dec 9, 2010
·Updated
Unspecified vulnerability in Movable Type 4.x before 4.35 and 5.x before 5.04 has unknown impact and attack vectors related to the "dynamic publishing error message."
Affected Software
17 affected components
Sixapart Movabletype=4.0
Sixapart Movabletype=4.1
Sixapart Movabletype=4.2
Sixapart Movabletype=4.3
Sixapart Movabletype=4.23
Sixapart Movabletype=4.25
Sixapart Movabletype=4.26
Sixapart Movabletype=4.31
Sixapart Movabletype=4.32
Sixapart Movabletype=4.33
Sixapart Movabletype=4.34
Sixapart Movabletype=4.261
Sixapart Movabletype=5.0-rc2
Sixapart Movabletype=5.01
Sixapart Movabletype=5.02
Sixapart Movabletype=5.03
Sixapart Movabletype=5.031
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-4511?
CVE-2010-4511 has an unspecified severity, but it is associated with potential vulnerabilities in Movable Type versions before 4.35 and 5.04.
2
How do I fix CVE-2010-4511?
To fix CVE-2010-4511, you should upgrade to Movable Type version 4.35 or 5.04 or later.
3
What versions of Movable Type are affected by CVE-2010-4511?
CVE-2010-4511 affects Movable Type versions 4.0 to 4.34 and versions 5.0 to 5.03.
4
What type of attack vectors are related to CVE-2010-4511?
CVE-2010-4511 relates to unspecified attack vectors concerning dynamic publishing error messages.
5
Is there a patch available for CVE-2010-4511?
Yes, the vulnerability can be mitigated by upgrading to a patched version of Movable Type such as 4.35 or 5.04.