Skip to content
Fencer Intel
high 7.5

CVE-2015-8562 in the critical feed json

Joomla! 1.5.x, 2.x, and 3.x before 3.4.6 allow remote attackers to conduct PHP object injection attacks and execute arbitrary PHP code via…

published 2015-12-16 10 y ago modified 2026-06-17 4 mo ago also EUVD-2015-8441

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
98.2%
EPSS 98.2% chance of exploitation in 30 days, percentile 99.9%
public exploits
3
Metasploit, Exploit-DB, plus a Nuclei check

Summary

Joomla! 1.5.x, 2.x, and 3.x before 3.4.6 allow remote attackers to conduct PHP object injection attacks and execute arbitrary PHP code via the HTTP User-Agent header, as exploited in the wild in December 2015.

Timeline

  1. First public exploit (Metasploit exploit/multi/http/joomla_http_header_rce)
  2. Published

Exploit prediction

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

Exploits and checks

  • Metasploit exploit/multi/http/joomla_http_header_rce Joomla HTTP Header Unauthenticated Remote Code Execution metasploit exploit, excellent rank, 2015-12-14
  • EDB-39033 Joomla! 1.5 < 3.4.6 - Object Injection 'x-forwarded-for' Header Remote Code Execution webapps, 2015-12-18
  • EDB-38977 Joomla! 1.5 < 3.4.5 - Object Injection Remote Command Execution webapps, 2015-12-15
  • Nuclei template Joomla HTTP Header Unauthenticated - Remote Code Execution nuclei detection template
  • packetstormsecurity.com http://packetstormsecurity.com/files/134949/Joomla-HTTP-Header-Unauthenticated-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
  • blog.sucuri.net https://blog.sucuri.net/2015/12/remote-command-execution-vulnerability-in-joomla.html 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-20 Improper Input Validation

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.