Skip to content
Fencer Intel
high 8.8

CVE-2017-14535 in the critical feed json

trixbox 2.8.0.4 has OS command injection via shell metacharacters in the lang parameter to /maint/modules/home/index.php.

published 2018-02-16 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-6036

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
50.1%
EPSS 50.1% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

trixbox 2.8.0.4 has OS command injection via shell metacharacters in the lang parameter to /maint/modules/home/index.php.

Timeline

  1. Published
  2. First public exploit (EDB-49913)

Exploit prediction

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

Exploits and checks

  • EDB-49913 Trixbox 2.8.0.4 - 'lang' Remote Code Execution (Unauthenticated) webapps, 2021-05-28
  • Nuclei template Trixbox - 2.8.0.4 OS Command Injection nuclei detection template
  • linkedin.com https://www.linkedin.com/pulse/trixbox-os-command-injection-vulnerability-sachin-wagh-ceh-ecsa-/?published=t referenced PoC, tagged "exploit" by a source, unverified
  • secur1tyadvisory.wordpress.com https://secur1tyadvisory.wordpress.com/2018/02/11/trixbox-os-command-injection-vulnerability-cve-2017-14535/ referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/162854/Trixbox-2.8.0.4-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/Hacker5preme/Exploits/tree/main/CVE-2017-14535-Exploit referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 9.0 AV:N/AC:L/Au:S/C:C/I:C/A:C

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS 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.