{"id":"CVE-2026-60167","url":"https://www.cyber-defence.io/tools/cve/CVE-2026-60167","generatedAt":"2026-10-28T02:11:42.222Z","title":"Vulnerability in the Oracle Hospitality Simphony product of Oracle Food and Beverage Applications (component: POS).","description":"Vulnerability in the Oracle Hospitality Simphony product of Oracle Food and Beverage Applications (component: POS).  Supported versions that are affected are 19.8-19.8.5, 19.9-19.9.3 and  19.10. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Hospitality Simphony.  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all Oracle Hospitality Simphony accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).","published":"2026-07-21T22:17:17.000Z","lastModified":"2026-10-24T19:10:00.000Z","status":"Analyzed","sourceIdentifier":"secalert_us@oracle.com","cvss":{"version":"3.1","score":7.5,"severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"},"cwe":["CWE-200"],"affected":["oracle/hospitality simphony"],"epss":{"score":0.00437,"percentile":0.37724,"date":"2026-10-26","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (0.44%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"https://www.oracle.com/security-alerts/cpujul2026.html","tags":["Vendor Advisory"],"source":"secalert_us@oracle.com"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-60167","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}