Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-60591 – Unauthenticated Data Tampering & DoS – Oracle Hospitality Simphony 19.8–19.10.1

Be the first to know when new zero-days emerge:

Summary

CVE-2026-60591 is a critical, easily exploitable vulnerability in the POS component of Oracle Hospitality Simphony. It allows an unauthenticated attacker with network access via HTTP to compromise the system, enabling unauthorized creation, deletion, or modification of critical data as well as denial-of-service conditions. Oracle disclosed the flaw in its August 2026 Critical Security Patch Update with a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: a flaw in the Point-of-Sale (POS) component of Oracle Hospitality Simphony that fails to properly restrict or authenticate operations affecting application data.
  • Trigger conditions: an attacker sends crafted HTTP requests to a network-reachable Simphony POS deployment; no login credentials or user interaction are required.
  • Attack vector: Network (AV:N), low attack complexity, no privileges or user interaction needed.
  • Impact: no confidentiality loss, but high impact to integrity and availability — attackers can create, delete, or modify critical POS data and disrupt service availability.

Affected software

  • Oracle Hospitality Simphony 19.8 through 19.8.5
  • Oracle Hospitality Simphony 19.9 through 19.9.3
  • Oracle Hospitality Simphony 19.10 through 19.10.1

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Mitigation and recommended actions

  • Immediate: Apply the fix provided in Oracle’s August 2026 Critical Security Patch Update for all affected Simphony 19.8, 19.9, and 19.10 installations, updating to the patched release for each branch as specified in the advisory.
  • If immediate patching is not possible: restrict network exposure of the Simphony POS component to trusted internal networks only, place it behind a firewall or VPN, and monitor for anomalous unauthenticated HTTP requests targeting POS data-modification endpoints until the patch can be applied.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Oracle MICROS Simphony
  • HTTP response header x-server-version: value beginning with EBO followed by a version number

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge