Cyber Resilience

CVE-2015-7611

RCE in Apache James Server 2.3.2

Public PoCHigh EPSSRCECommand Injection
Published
07 June 2016
Modified
06 May 2026
Patch / advisory
View advisory
CVSS Score v3 8.1
Click a component to see what it means
Raw vectorCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.69 99.3th percentile
Risk Priority 81 floored blend · peak EPSS

Summary

CVE-2015-7611 is a high-severity OS Command Injection (CWE-78) vulnerability in Apache James Server. Its CVSS base score is 8.1 (High).

Operationally, ranked in the top 0.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

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

CWE(s)
CWE-78

Related Threats

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1190 Exploit Public-Facing Application Initial Accessconfidence: HIGH
The CVE describes remote command execution on a public-facing mail server via unspecified vectors, directly mapping to exploitation of a public-facing application.
attack.mitre.org →
T1059 Command and Scripting Interpreter Executionconfidence: HIGH
CWE-78 OS command injection enables arbitrary system command execution on the compromised server.
attack.mitre.org →
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-54941Same vendor: Apache
CVE-2020-11978Same vendor: Apache
CVE-2022-24288Same vendor: Apache
CVE-2022-24697Same vendor: Apache
CVE-2022-33891Same vendor: Apache
CVE-2020-1956Same vendor: Apache
CVE-2026-62392Same vendor: Apache
CVE-2021-38294Same vendor: Apache
CVE-2026-34197Same vendor: Apache
CVE-2021-21315Same vendor: Apache

Affected Assets

apache
james server
2.3.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.5
  • V1.2.8
  • V15.2.5

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SC-27 Platform-independent Applications
addresses: CWE-78

Platform-independent apps typically execute inside a managed runtime or sandbox that restricts direct OS command execution, reducing the ability to exploit OS command injection.

SI-10 Information Input Validation
addresses: CWE-78

Validates inputs to block special elements that would alter OS command execution.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

PR.PS-06's SDLC practices directly require secure coding and input handling that blocks command-injection defects, yet the single broad outcome leaves many specific neutralization vectors and verification gaps unaddressed.

PR.PS-02 partial match
prevents

Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.

References