Skip to content
Fencer Intel
medium 6.5

CVE-2015-5453 json

Watchguard XCS 9.2 and 10.0 before build 150522 allow remote authenticated users to execute arbitrary commands via shell metacharacters in…

published 11y ago modified 4mo ago also EUVD-2015-5409

cvss
6.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
58.4%
EPSS 58.4% chance of exploitation in 30 days, percentile 99.1%
public exploits
2
Metasploit and Exploit-DB

Summary

Watchguard XCS 9.2 and 10.0 before build 150522 allow remote authenticated users to execute arbitrary commands via shell metacharacters in the id parameter to ADMIN/mailqueue.spl.

Is CVE-2015-5453 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/freebsd/http/watchguard_cmd_exec)
  2. Published

Exploit prediction

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

Exploits and checks

  • Metasploit exploit/freebsd/http/watchguard_cmd_exec Watchguard XCS Remote Command Execution metasploit exploit, excellent rank, 2015-06-29
  • EDB-38346 Watchguard XCS - Remote Command Execution (Metasploit) remote, 2015-09-28
  • packetstormsecurity.com http://packetstormsecurity.com/files/132498/Watchguard-XCS-10.0-SQL-Injection-Command-Execution.html referenced PoC, tagged "exploit" by a source, unverified
  • security-assessment.com http://www.security-assessment.com/files/documents/advisory/Watchguard-XCS-final.pdf referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/133721/Watchguard-XCS-Remote-Command-Execution.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Classification

Weakness
  • CWE-77 Improper Neutralization of Special Elements used in a 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.