CVE-2014-7228 in the critical feed json
Akeeba Restore (restore.php), as used in Joomla!
published 2014-11-03 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-7100
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 56.0%
- EPSS 56.0% chance of exploitation in 30 days, percentile 99%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
Akeeba Restore (restore.php), as used in Joomla! 2.5.4 through 2.5.25, 3.x through 3.2.5, and 3.3.0 through 3.3.4; Akeeba Backup for Joomla! Professional 3.0.0 through 4.0.2; Backup Professional for WordPress 1.0.b1 through 1.1.3; Solo 1.0.b1 through 1.1.2; Admin Tools Core and Professional 2.0.0 through 2.4.4; and CMS Update 1.0.a1 through 1.0.1, when performing a backup or update for an archive, does not delete parameters from $_GET and $_POST when it is cleansing $_REQUEST, but later accesses $_GET and $_POST using the getQueryParam function, which allows remote attackers to bypass encryption and execute arbitrary code via a command message that extracts a crafted archive.
Timeline
- First public exploit (Metasploit exploit/unix/webapp/joomla_akeeba_unserialize)
- Published
Exploit prediction
56.05% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/unix/webapp/joomla_akeeba_unserialize Joomla Akeeba Kickstart Unserialize Remote Code Execution metasploit exploit, excellent rank, 2014-09-29
- EDB-35033 Joomla! Component Akeeba Kickstart - Unserialize Remote Code Execution (Metasploit) remote, 2014-10-21
- websec.wordpress.com http://websec.wordpress.com/2014/10/05/joomla-3-3-4-akeeba-kickstart-remote-code-execution-cve-2014-7228/ 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
-
- CWE-310 Cryptographic Issues
References
Sources
- CVE List CVE-2014-7228
- NVD CVE-2014-7228
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.