Skip to content
Fencer Intel
high 7.5

CVE-2015-2208 in the critical feed json

The saveObject function in moadmin.php in phpMoAdmin 1.1.2 allows remote attackers to execute arbitrary commands via shell metacharacters i…

published 11y ago modified 4mo ago also EUVD-2015-2315

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

Summary

The saveObject function in moadmin.php in phpMoAdmin 1.1.2 allows remote attackers to execute arbitrary commands via shell metacharacters in the object parameter.

Is CVE-2015-2208 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/phpmoadmin_exec)
  2. Published

Exploit prediction

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

Exploits and checks

  • Metasploit exploit/multi/http/phpmoadmin_exec PHPMoAdmin 1.1.2 Remote Code Execution metasploit exploit, excellent rank, 2015-03-03
  • EDB-36251 PHPMoAdmin - Unauthorized Remote Code Execution webapps, 2015-03-03
  • seclists.org http://seclists.org/fulldisclosure/2015/Mar/19 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/130685/PHPMoAdmin-1.1.2-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
  • openwall.com http://www.openwall.com/lists/oss-security/2015/03/04/4 referenced PoC, tagged "exploit" by a source, unverified
  • openwall.com http://www.openwall.com/lists/oss-security/2015/03/04/5 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-77 Improper Neutralization of Special Elements used in a Command

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.