CVE-2015-2208

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 62.0% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
7.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 62%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 62%CVSS v2: 7.5Exploit: Metasploit · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5(low)
EG Risk
64(Track)
EG Risk 64/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
62%
EPSS %ILE
99%
KEV
Not listed

Published

March 12, 2015

Last Modified

May 6, 2026

References (10)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-26 14:50 UTCEPSS rescore
  2. 2026-07-26 13:53 UTCEG score recompute▲ 7.50
  3. 2026-07-24 14:13 UTCEPSS rescore
  4. 2026-07-23 14:14 UTCEPSS rescore
  5. 2026-07-23 01:16 UTCEG score recompute▼ 5.20
  6. 2026-07-23 00:19 UTCEG score recompute▲ 5.20
  7. 2026-07-22 21:57 UTCEG score recompute▼ 9.00
  8. 2026-07-22 14:04 UTCEPSS rescore
  9. 2026-07-21 15:21 UTCEPSS rescore
  10. 2026-07-21 15:21 UTCEPSS rescore
  11. 2026-07-20 17:03 UTCEPSS rescore
  12. 2026-07-19 02:26 UTCEPSS rescore
  13. 2026-07-19 02:26 UTCEPSS rescore
  14. 2026-07-16 16:59 UTCEPSS rescore
  15. 2026-07-16 16:59 UTCEPSS rescore
  16. 2026-07-15 16:54 UTCEPSS rescore
  17. 2026-07-15 16:54 UTCEPSS rescore
  18. 2026-07-15 01:56 UTCEPSS rescore
  19. 2026-07-13 22:26 UTCEPSS rescore
  20. 2026-07-11 08:23 UTCEPSS rescore
  21. 2026-07-09 19:05 UTCEPSS rescore
  22. 2026-07-06 16:24 UTCEPSS rescore
  23. 2026-07-06 02:20 UTCEPSS rescore
  24. 2026-07-05 02:26 UTCEPSS rescore
  25. 2026-07-02 15:21 UTCEPSS rescore
Show 45 more
  1. 2026-07-01 15:02 UTCEPSS rescore
  2. 2026-07-01 15:02 UTCEPSS rescore
  3. 2026-06-28 04:53 UTCEPSS rescore
  4. 2026-06-27 03:05 UTCEPSS rescore
  5. 2026-06-25 13:47 UTCEPSS rescore
  6. 2026-06-25 13:47 UTCEPSS rescore
  7. 2026-06-24 14:02 UTCEPSS rescore
  8. 2026-06-24 14:02 UTCEPSS rescore
  9. 2026-06-23 21:30 UTCEPSS rescore
  10. 2026-06-22 14:23 UTCEPSS rescore
  11. 2026-06-22 14:22 UTCEPSS rescore
  12. 2026-06-21 01:57 UTCEPSS rescore
  13. 2026-06-21 01:57 UTCEPSS rescore
  14. 2026-06-19 19:23 UTCEPSS rescore
  15. 2026-06-19 19:23 UTCEPSS rescore
  16. 2026-06-18 17:50 UTCEPSS rescore
  17. 2026-06-18 17:49 UTCEPSS rescore
  18. 2026-06-17 17:49 UTCEPSS rescore
  19. 2026-06-16 17:50 UTCEPSS rescore
  20. 2026-06-16 17:49 UTCEPSS rescore
  21. 2026-06-15 17:45 UTCEPSS rescore
  22. 2026-06-13 22:57 UTCEPSS rescore
  23. 2026-06-12 23:09 UTCEPSS rescore
  24. 2026-06-10 22:15 UTCEPSS rescore
  25. 2026-06-05 22:44 UTCEPSS rescore
  26. 2026-06-04 13:10 UTCEPSS rescore
  27. 2026-06-04 13:09 UTCEPSS rescore
  28. 2026-06-02 20:10 UTCEPSS rescore
  29. 2026-06-02 20:10 UTCEPSS rescore
  30. 2026-06-01 13:49 UTCEPSS rescore
  31. 2026-06-01 13:49 UTCEPSS rescore
  32. 2026-05-29 13:41 UTCEPSS rescore
  33. 2026-05-28 13:42 UTCEPSS rescore
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:11 UTCEG score recompute
  36. 2026-05-28 13:11 UTCGHSA enrichment
  37. 2026-05-26 07:16 UTCEPSS rescore
  38. 2026-05-26 07:16 UTCEPSS rescore
  39. 2026-05-24 16:43 UTCEPSS rescore
  40. 2026-05-23 15:10 UTCEPSS rescore
  41. 2026-05-21 22:40 UTCEPSS rescore
  42. 2026-05-20 22:37 UTCEPSS rescore
  43. 2026-05-20 22:37 UTCEPSS rescore
  44. 2026-05-18 21:30 UTCEPSS rescore
  45. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCptantiku/cve-2015-2208
    First seen Apr 11, 2015

    Docker simulating cve-2015-2208 vulnerability

    Open source ↗
  • Exploit-DBEDB-36251
    First seen Mar 3, 2015

    PHPMoAdmin - Unauthorized Remote Code Execution

    Open source ↗
  • Metasploitexploit/multi/http/phpmoadmin_exec✓ verified
    First seen Mar 3, 2015

    PHPMoAdmin 1.1.2 Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2015-2208?
CVE-2015-2208 is a high vulnerability published on March 12, 2015. 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.
When was CVE-2015-2208 disclosed?
CVE-2015-2208 was first published in the National Vulnerability Database on March 12, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-2208 actively exploited?
CVE-2015-2208 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 62% probability of exploitation in the next 30 days, which ranks it in the top 0.9% of all scored CVEs.
How do I remediate CVE-2015-2208?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-2208, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2015-2208

Explore →

Is Your Infrastructure Affected by CVE-2015-2208?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs