# CVE-2018-2636: Auth bypass in Hospitality Simphony

> Unauthenticated attackers can compromise Oracle Hospitality Simphony via HTTP, leading to full system takeover.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2018
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-fc59-v87q-7frq

## What is CVE-2018-2636?

CVE-2018-2636 is a high-severity authentication bypass vulnerability in Oracle Corporation Hospitality Simphony, published on 18 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Hospitality Simphony component of Oracle Hospitality Applications (subcomponent: Security). Supported versions that are affected are 2.7, 2.8 and 2.9. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Hospitality Simphony. Successful attacks of this vulnerability can result in takeover of Oracle Hospitality Simphony. CVSS 3.0 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

## Which versions are affected by CVE-2018-2636?

It affects 1 product.


Products: Oracle Hospitality Simphony.

## How do I fix CVE-2018-2636?

No fix has been published for CVE-2018-2636 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-2636 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-2636 exists.

Public exploit code:

- ERPScan Public POC for CVE-2018-2636 (github_poc): https://github.com/erpscanteam/CVE-2018-2636
- MICROS Honeypot is a low interaction honeypot to detect CVE-2018-2636 in the Oracle Hospitality Simphony component of Oracle Hospitality Applications (MICROS). This is a directory traversal vulnerability. (github_poc): https://github.com/Cymmetria/micros_honeypot
- Oracle Hospitality Simphony (MICROS) 2.7 < 2.9 - Directory Traversal (exploitdb)

## Other vulnerabilities in Oracle Corporation Hospitality Simphony

- [CVE-2024-20997](https://insights.sbomify.com/CVE-2024-20997/): Auth bypass in Hospitality Simphony (critical 9.9)
- [CVE-2024-21010](https://insights.sbomify.com/CVE-2024-21010/): Missing authorization in Hospitality Simphony (critical 9.9)
- [CVE-2024-21014](https://insights.sbomify.com/CVE-2024-21014/): Auth bypass in Hospitality Simphony (critical 9.8)
- [CVE-2026-60591](https://insights.sbomify.com/CVE-2026-60591/): Missing authorization in Oracle Hospitality Simphony (critical 9.1)
- [CVE-2026-60168](https://insights.sbomify.com/CVE-2026-60168/): Missing authorization in Oracle Hospitality Simphony (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-2636 and fix it if it is affected.

What it is: CVE-2018-2636 is a high-severity authentication bypass vulnerability in Oracle Corporation Hospitality Simphony, published on 18 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-2636 exists.

Affected product: Oracle Corporation Hospitality Simphony. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-2636/ (Markdown: https://insights.sbomify.com/CVE-2018-2636/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-2636
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-2636
- OSV: https://osv.dev/vulnerability/CVE-2018-2636

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-2636/
Summaries are generated and may contain mistakes; the official description above is the record.