Skip to content
Fencer Intel
high 8.8

CVE-2018-5406 in the critical feed json

The Quest Kace K1000 Appliance misconfigures the Cross-Origin Resource Sharing (CORS) mechanism.

published 2019-06-03 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-17176

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
12.2%
EPSS 12.2% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

The Quest Kace K1000 Appliance, versions prior to 9.0.270, allows a remote attacker to exploit the misconfigured Cross-Origin Resource Sharing (CORS) mechanism. An unauthenticated, remote attacker could exploit this vulnerability to perform sensitive actions such as adding a new administrator account or changing the appliance’s settings. A malicious internal user could also gain administrator privileges of this appliance and use it to visit a malicious link that exploits this vulnerability. This could cause the application to perform sensitive actions such as adding a new administrator account or changing the appliance’s settings. An unauthenticated, remote attacker could add an administrator-level account or change the appliance's settings.

Patch / fix

  • quest kace_systems_management_appliance_firmware 9.0.270

Timeline

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

Exploit prediction

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

Exploits and checks

  • EDB-46956 KACE System Management Appliance (SMA) < 9.0.270 - Multiple Vulnerabilities webapps, 2019-06-03
  • packetstormsecurity.com http://packetstormsecurity.com/files/153150/Dell-KACE-System-Management-Appliance-SMA-XSS-SQL-Injection.html 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:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected products

  • Quest Kace K1000 Appliance

Classification

Weakness

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.