7.5
CWE
17
Advisory Published
CVE Published
Updated

CVE-2013-2184

First published: Mon Jun 17 2013(Updated: )

Movable Type before 5.2.6 does not properly use the Storable::thaw function, which allows remote attackers to execute arbitrary code via the comment_state parameter.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
debian/movabletype-opensource
debian/movabletype-opensource<=5.1.4+dfsg-4<=5.1.4+dfsg-5
5.1.4+dfsg-4+deb7u2
Six Apart Movable Type<=5.2.5

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2013-2184?

    CVE-2013-2184 is considered to have a high severity due to its potential for remote code execution.

  • How do I fix CVE-2013-2184?

    To fix CVE-2013-2184, upgrade Movable Type to version 5.2.6 or later.

  • Which versions of Movable Type are affected by CVE-2013-2184?

    CVE-2013-2184 affects Movable Type versions prior to 5.2.6.

  • Can CVE-2013-2184 be exploited by attackers?

    Yes, CVE-2013-2184 can be exploited by remote attackers to execute arbitrary code.

  • What components are vulnerable in CVE-2013-2184?

    CVE-2013-2184 primarily involves the improper use of the Storable::thaw function in the Movable Type application.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203