# CVE-2018-0396: Cross-site scripting in Cisco Unified Communications Manager IM And Presence Service unknown

> Authenticated remote attackers can execute arbitrary script code or access sensitive browser-based information via insufficient input validation in the web interface.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jul 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-pfw4-5446-c4cv

## What is CVE-2018-0396?

CVE-2018-0396 is a medium-severity cross-site scripting vulnerability in Cisco Unified Communications Manager IM And Presence Service unknown, published on 18 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the web framework of the Cisco Unified Communications Manager IM and Presence Service software could allow an authenticated, remote attacker to conduct a cross-site scripting (XSS) attack against the user of the web interface of an affected system. The vulnerability is due to insufficient input validation of certain parameters passed to the web server. An attacker could exploit this vulnerability by convincing the user to access a malicious link or by intercepting the user request and injecting certain malicious code. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected site or allow the attacker to access sensitive browser-based information. Cisco Bug IDs: CSCve25985.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Cisco Unified Communications Manager Im and Presence Service.

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

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

## Is CVE-2018-0396 being exploited?

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

## Other vulnerabilities in Cisco Unified Communications Manager IM And Presence Service unknown

- [CVE-2018-0363](https://insights.sbomify.com/CVE-2018-0363/): Cross-site request forgery in Cisco Unified Communications Manager IM & Presence Service unknown (high 8.8)
- [CVE-2023-20108](https://insights.sbomify.com/CVE-2023-20108/): Denial of service in Cisco Unified Communications Manager IM and Presence Service (high 7.5)
- [CVE-2016-6464](https://insights.sbomify.com/CVE-2016-6464/): Information disclosure in Cisco Unified Communications Manager (high 7.5)
- [CVE-2016-1466](https://insights.sbomify.com/CVE-2016-1466/): Denial of service in n/a (high 7.5)
- [CVE-2021-1363](https://insights.sbomify.com/CVE-2021-1363/): Cisco Unified Communications Manager IM & Presence Service SQL Injection Vulnerabilities (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-0396 is a medium-severity cross-site scripting vulnerability in Cisco Unified Communications Manager IM And Presence Service unknown, published on 18 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-0396 in the wild and no public exploit code.

Affected product: Cisco Unified Communications Manager IM And Presence Service unknown. 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-0396/ (Markdown: https://insights.sbomify.com/CVE-2018-0396/index.md)
```

## Sources

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

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