CVE-2015-7611

HIGHNVD 8.18.7▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.7 because EPSS predicts 69% probability of exploitation within the next 30 days (top 0.7% of all CVEs). NVD baseline CVSS 8.1 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
8.1
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 69%
CISA-KEV: Not listedEPSS: 69%CVSS: 8.1Exploit: NoneExposed: 0

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

Apache James Server 2.3.2, when configured with file-based user repositories, allows attackers to execute arbitrary system commands via unspecified vectors.

CVSS v3
8.1
EG Score
8.7(high)
EG Risk
71(Track)
EG Risk 71/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
Severity87% × 45%
Exploitation69% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.3%
KEV
Not listed

Published

June 7, 2016

Last Modified

May 6, 2026

References (12)

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.james:james-server—2.3.2.1—

Data Freshness Timeline

(refreshed 8× in last 7d / 29× 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-23 01:19 UTCEG score recompute
  2. 2026-07-23 00:21 UTCEG score recompute▲ 0.60
  3. 2026-07-22 21:59 UTCEG score recompute
  4. 2026-07-22 14:04 UTCEPSS rescore
  5. 2026-07-20 17:03 UTCEPSS rescore
  6. 2026-07-19 14:27 UTCEPSS rescore
  7. 2026-07-19 14:27 UTCEPSS rescore
  8. 2026-07-18 10:00 UTCEPSS rescore
  9. 2026-07-15 16:54 UTCEPSS rescore
  10. 2026-07-15 16:54 UTCEPSS rescore
  11. 2026-07-12 05:42 UTCEPSS rescore
  12. 2026-07-11 08:23 UTCEPSS rescore
  13. 2026-07-09 19:05 UTCEPSS rescore
  14. 2026-07-09 19:05 UTCEPSS rescore
  15. 2026-07-08 15:10 UTCEPSS rescore
  16. 2026-07-06 02:20 UTCEPSS rescore
  17. 2026-07-05 02:26 UTCEPSS rescore
  18. 2026-07-04 06:28 UTCEPSS rescore
  19. 2026-07-01 15:02 UTCEPSS rescore
  20. 2026-06-30 23:19 UTCEPSS rescore
  21. 2026-06-30 23:19 UTCEPSS rescore
  22. 2026-06-28 14:04 UTCEPSS rescore
  23. 2026-06-28 04:53 UTCEPSS rescore
  24. 2026-06-27 03:05 UTCEPSS rescore
  25. 2026-06-25 13:47 UTCEPSS rescore
Show 43 more
  1. 2026-06-25 13:47 UTCEPSS rescore
  2. 2026-06-24 14:02 UTCEPSS rescore
  3. 2026-06-24 14:02 UTCEPSS rescore
  4. 2026-06-23 21:30 UTCEPSS rescore
  5. 2026-06-19 19:23 UTCEPSS rescore
  6. 2026-06-19 19:23 UTCEPSS rescore
  7. 2026-06-18 17:50 UTCEPSS rescore
  8. 2026-06-17 17:50 UTCEPSS rescore
  9. 2026-06-17 17:49 UTCEPSS rescore
  10. 2026-06-16 17:50 UTCEPSS rescore
  11. 2026-06-16 17:50 UTCEPSS rescore
  12. 2026-06-15 17:45 UTCEPSS rescore
  13. 2026-06-14 23:14 UTCEPSS rescore
  14. 2026-06-13 22:57 UTCEPSS rescore
  15. 2026-06-12 23:09 UTCEPSS rescore
  16. 2026-06-12 23:09 UTCEPSS rescore
  17. 2026-06-11 13:57 UTCEPSS rescore
  18. 2026-06-11 13:57 UTCEPSS rescore
  19. 2026-06-10 22:15 UTCEPSS rescore
  20. 2026-06-10 13:18 UTCEPSS rescore
  21. 2026-06-08 14:14 UTCEPSS rescore
  22. 2026-06-07 15:22 UTCEPSS rescore
  23. 2026-06-06 13:45 UTCEPSS rescore
  24. 2026-06-05 22:44 UTCEPSS rescore
  25. 2026-06-05 06:08 UTCEPSS rescore
  26. 2026-06-05 06:08 UTCEPSS rescore
  27. 2026-06-02 20:10 UTCEPSS rescore
  28. 2026-06-01 13:49 UTCEPSS rescore
  29. 2026-06-01 13:49 UTCEPSS rescore
  30. 2026-05-31 22:28 UTCEPSS rescore
  31. 2026-05-31 22:28 UTCEPSS rescore
  32. 2026-05-31 00:14 UTCEPSS rescore
  33. 2026-05-29 13:41 UTCEPSS rescore
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-27 13:38 UTCEPSS rescore
  37. 2026-05-27 13:38 UTCEPSS rescore
  38. 2026-05-26 07:16 UTCEPSS rescore
  39. 2026-05-26 07:16 UTCEPSS rescore
  40. 2026-05-24 16:43 UTCEPSS rescore
  41. 2026-05-22 20:07 UTCEG score recompute
  42. 2026-05-18 21:30 UTCEPSS rescore
  43. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(2 references)

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

  • Exploit-DBEDB-48130✓ verified
    First seen Feb 24, 2020

    Apache James Server 2.3.2 - Insecure User Creation Arbitrary File Write (Metasploit)

    Open source ↗
  • Metasploitexploit/linux/smtp/apache_james_exec✓ verified
    First seen Oct 1, 2015

    Apache James Server 2.3.2 Insecure User Creation Arbitrary File Write

    Open source ↗

Frequently asked(5)

What is CVE-2015-7611?
CVE-2015-7611 is a high vulnerability published on June 7, 2016. Apache James Server 2.3.2, when configured with file-based user repositories, allows attackers to execute arbitrary system commands via unspecified vectors.
When was CVE-2015-7611 disclosed?
CVE-2015-7611 was first published in the National Vulnerability Database on June 7, 2016, 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-7611 actively exploited?
CVE-2015-7611 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2015-7611?
CVE-2015-7611 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.7.
How do I remediate CVE-2015-7611?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-7611, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-7611

Explore →

Is Your Infrastructure Affected by CVE-2015-7611?

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

Start Free Scan →Browse All CVEs