# CVE-2018-2756: Information disclosure in Communications Order and Service Management

> Low-privileged attackers can access critical data and modify some records in Oracle Communications Order and Service Management via HTTP with user interaction.

- **Severity:** Medium 6.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Apr 2018
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-5w8h-j6m2-m2p5

## What is CVE-2018-2756?

CVE-2018-2756 is a medium-severity vulnerability in Oracle Corporation Communications Order and Service Management, published on 19 Apr 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Communications Order and Service Management component of Oracle Communications Applications (subcomponent: WebUI). Supported versions that are affected are 7.2.4.3.0, 7.3.0.1.x, 7.3.1.0.7 and 7.3.5.0.x. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Communications Order and Service Management. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Communications Order and Service Management accessible data as well as unauthorized update, insert or delete access to some of Oracle Communications Order and Service Management accessible data. CVSS 3.0 Base Score 6.3 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N).

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

It affects 1 product.


Products: Oracle Communications Order and Service Management.

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

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

## Is CVE-2018-2756 being exploited?

There is no known exploitation of CVE-2018-2756 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Corporation Communications Order and Service Management

- [CVE-2025-21542](https://insights.sbomify.com/CVE-2025-21542/): Missing authorization in Oracle Communications Order and Service Management (medium 6.3)
- [CVE-2018-2567](https://insights.sbomify.com/CVE-2018-2567/): Cross-site scripting in Communications Order and Service Management (medium 6.1)
- [CVE-2025-30729](https://insights.sbomify.com/CVE-2025-30729/): Missing authorization in Oracle Communications Order and Service Management (medium 5.5)
- [CVE-2025-21544](https://insights.sbomify.com/CVE-2025-21544/): Missing authorization in Oracle Communications Order and Service Management (medium 5.4)
- [CVE-2025-21554](https://insights.sbomify.com/CVE-2025-21554/): Missing authorization in Oracle Communications Order and Service Management (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-2756 is a medium-severity vulnerability in Oracle Corporation Communications Order and Service Management, published on 19 Apr 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-2756 in the wild and no public exploit code.

Affected product: Oracle Corporation Communications Order and Service Management. 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-2756/ (Markdown: https://insights.sbomify.com/CVE-2018-2756/index.md)
```

## Sources

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

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