CVE-2026-60591: Vulnerability in the Oracle Hospitality Simphony product of Oracle Food and Beverage Applications (componen...
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-19.10.1. 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 creation, deletion or modification access to critical data or all Oracle Hospitality Simphony accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Hospitality Simphony. CVSS 3.1 Base Score 9.1 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H).
Security readout for executives and security teams
Plain-English summary
Oracle Hospitality Simphony POS contains a critical authentication weakness. An attacker who can reach the affected HTTP service may alter or delete critical application data and repeatedly crash the system without credentials or user interaction. This threatens transaction integrity and service availability, although the supplied sources do not identify confidentiality loss.
Executive priority
Treat as an immediate remediation priority for affected production POS environments. The combination of unauthenticated network access, critical data manipulation, and complete denial of service could disrupt hospitality operations. Accelerate inventory and isolation while obtaining Oracle's approved remediation; emergency attention is especially warranted for broadly reachable systems.
Technical view
CVE-2026-60591 affects Simphony 19.8–19.8.5, 19.9–19.9.3, and 19.10–19.10.1. It is classified as CWE-306, indicating missing authentication for a critical function. CVSS 3.1 is 9.1: network-accessible, low complexity, unauthenticated, no interaction, with high integrity and availability impact but no stated confidentiality impact.
Likely exposure
Highest risk applies where affected Simphony POS HTTP services are reachable from the internet, guest networks, vendor connections, or other untrusted network segments. Internal-only systems remain exposed to attackers or compromised devices with network access. The supplied evidence does not identify specific endpoints or default configurations.
Exploitation context
The vulnerability is described as easily exploitable remotely over HTTP without authentication or user interaction. The supplied bundle reports that it is not listed in KEV and provides no evidence of active exploitation, public proof-of-concept code, or observed attacks.
Researcher notes
The stated vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H. Evidence supports authentication bypass or absence at a critical function level, but does not disclose the vulnerable endpoint, request mechanics, root cause, patch identifier, or exploitation telemetry. Avoid assuming impacts beyond Simphony-accessible data and service availability.
Mitigation direction
Identify installations within the specifically affected Simphony version ranges.
Restrict HTTP access to trusted management and application networks.
Review Oracle's advisory for approved patches or upgrade guidance.
Prioritize backups and recovery readiness for critical Simphony data.
Monitor vendor guidance for updated remediation and threat information.
Validation and detection
Confirm each Simphony deployment's exact installed version and component inventory.
Map every network path that can reach the Simphony HTTP service.
Verify segmentation and access controls block untrusted sources.
Review logs for unexplained data changes, hangs, or repeated crashes.
After remediation, confirm the installed version matches Oracle guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Functionality
Missing Authentication for Critical Functionality represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.