Skip to content
Fencer Intel
high 7.5

CVE-2013-0209 in the critical feed json

lib/MT/Upgrade.pm in mt-upgrade.cgi in Movable Type 4.2x and 4.3x through 4.38 does not require authentication for requests to database-mig…

published 13y ago modified 4mo ago also EUVD-2013-0244

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
45.2%
EPSS 45.2% chance of exploitation in 30 days, percentile 98%
public exploits
2
Metasploit and Exploit-DB

Summary

lib/MT/Upgrade.pm in mt-upgrade.cgi in Movable Type 4.2x and 4.3x through 4.38 does not require authentication for requests to database-migration functions, which allows remote attackers to conduct eval injection and SQL injection attacks via crafted parameters, as demonstrated by an eval injection attack against the core_drop_meta_for_table function, leading to execution of arbitrary Perl code.

Patch / fix

Is CVE-2013-0209 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/multi/http/movabletype_upgrade_exec)
  2. Published

Exploit prediction

45.20% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/multi/http/movabletype_upgrade_exec Movable Type 4.2x, 4.3x Web Upgrade Remote Code Execution metasploit exploit, excellent rank, 2013-01-07
  • EDB-24321 Movable Type 4.2x/4.3x - Web Upgrade Remote Code Execution (Metasploit) remote, 2013-01-07
  • sec-1.com http://www.sec-1.com/blog/?p=402 referenced PoC, tagged "exploit" by a source, unverified
  • sec-1.com http://www.sec-1.com/blog/wp-content/uploads/2013/01/movabletype_upgrade_exec.rb_.txt referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.