CVE-2013-2184 json
Movable Type before 5.2.6 does not properly use the Storable::thaw function, which allows remote attackers to execute arbitrary code via th…
published 11y ago modified 4mo ago also EUVD-2013-2143
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.6%
- EPSS 3.6% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2013-2184 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 FencerExploit prediction
3.61% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
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
-
- CWE-17 DEPRECATED: Code
References
-
debian.org
/security/2015/dsa-3183
vendor-advisory
-
movabletype.org
/documentation/appendices/release-notes/movable-type-526-release-notes.html
vendor-advisory
-
seclists.org
/oss-sec/2013/q2/568
mailing-list
-
seclists.org
/oss-sec/2013/q2/560
mailing-list
Sources
- CVE List CVE-2013-2184
- NVD CVE-2013-2184
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.