VYPR
Unrated severityNVD Advisory· Published Nov 3, 2014· Updated May 6, 2026

CVE-2014-7228

CVE-2014-7228

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Akeeba Restore in multiple Akeeba and Joomla! products allows remote attackers to bypass encryption and execute arbitrary code by exploiting improper parameter cleansing during archive extraction.

Vulnerability

The vulnerability resides in restore.php used by Akeeba Restore, which is included in multiple products: 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 [2]. When performing a backup or update, the masterSetup() function checks for the existence of restoration.php and includes it. The getQueryParam() function retrieves parameters from $_GET and $_POST without properly cleansing $_REQUEST, allowing an attacker to bypass the AES-128 CTR encryption used to authenticate commands [1].

Exploitation

An unauthenticated remote attacker can exploit this vulnerability only during the brief window when a backup archive or Joomla! update package is being extracted, because restoration.php exists only at that time [2]. The attacker sends crafted HTTP requests to restore.php with parameters that bypass the encryption check, enabling the extraction of a malicious archive [1]. The attack requires no authentication and no user interaction beyond the legitimate extraction process.

Impact

Successful exploitation allows the attacker to execute arbitrary PHP code on the server, leading to full compromise of the Joomla! installation or affected application [1]. The attacker gains the same privileges as the web server user, typically resulting in complete disclosure, modification, or destruction of data.

Mitigation

Akeeba released security updates in September 2014 [2]. Affected users should upgrade to the latest versions: Joomla! 3.3.5 or later, Akeeba Backup for Joomla! Professional 4.0.3 or later, Backup Professional for WordPress 1.1.4 or later, Solo 1.1.3 or later, Admin Tools Core and Professional 2.4.5 or later, and CMS Update 1.0.2 or later [2]. No workaround is available; the only mitigation is to apply the patches. The vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog.

AI Insight generated on May 23, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

48
  • Joomla/Joomla!45 versions
    cpe:2.3:a:joomla:joomla\!:2.5.10:*:*:*:*:*:*:*+ 44 more
    • cpe:2.3:a:joomla:joomla\!:2.5.10:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.11:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.12:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.13:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.14:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.15:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.16:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.17:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.18:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.19:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.20:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.21:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.22:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.23:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.24:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.25:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.4:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.5:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.6:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.7:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.8:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:2.5.9:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.0.0:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.0.1:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.0.2:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.0.3:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.0.4:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.1.0:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.1.1:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.1.2:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.1.3:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.1.4:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.1.5:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.1.6:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.2.0:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.2.1:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.2.2:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.2.3:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.2.4:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.2.5:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.3.0:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.3.1:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.3.2:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.3.3:*:*:*:*:*:*:*
    • cpe:2.3:a:joomla:joomla\!:3.3.4:*:*:*:*:*:*:*
  • Range: 3.0.0 through 4.0.2
  • Range: 1.0.b1 through 1.1.3
  • Akeeba/Solollm-create
    Range: 1.0.b1 through 1.1.2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

3

News mentions

0

No linked articles in our index yet.