# CVE-2016-9723: Cross-site scripting in QRadar SIEM

> An attacker can inject JavaScript into the IBM QRadar Web UI to steal credentials from trusted sessions.

- **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:** 7 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wcrj-6369-2hmf

## What is CVE-2016-9723?

CVE-2016-9723 is a medium-severity cross-site scripting vulnerability in Ibm Qradar Security Information and Event Manager, published on 7 Mar 2017. 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

IBM QRadar 7.2 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM Reference #: 1999534.

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

## Which versions are affected by CVE-2016-9723?

It affects 2 products.


Products: Ibm Qradar Incident Forensics, Ibm Qradar Security Information and Event Manager.

## How do I fix CVE-2016-9723?

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

## Is CVE-2016-9723 being exploited?

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

## Other vulnerabilities in Ibm Qradar Security Information and Event Manager

- [CVE-2016-9726](https://insights.sbomify.com/CVE-2016-9726/): Command injection in IBM Security QRadar SIEM 7.1 MR1, 7.1, 7.0, 7.2, 7.1 MR2, 7, 7.1 MR2, 7.2.3 (high 8.8)
- [CVE-2016-9727](https://insights.sbomify.com/CVE-2016-9727/): Command injection in QRadar SIEM (high 8.5)
- [CVE-2025-33120](https://insights.sbomify.com/CVE-2025-33120/): IBM QRadar SIEM privilege escalation (high 7.8)
- [CVE-2018-1649](https://insights.sbomify.com/CVE-2018-1649/): Path traversal in QRadar Incident Forensics (high 7.7)
- [CVE-2018-1648](https://insights.sbomify.com/CVE-2018-1648/): Weak cryptography in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9723 and fix it if it is affected.

What it is: CVE-2016-9723 is a medium-severity cross-site scripting vulnerability in Ibm Qradar Security Information and Event Manager, published on 7 Mar 2017. 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-2016-9723 in the wild and no public exploit code.

Affected product: Ibm Qradar Security Information and Event Manager. 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-2016-9723/ (Markdown: https://insights.sbomify.com/CVE-2016-9723/index.md)
```

## Sources

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

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