# CVE-2018-18985: Cross-site scripting in Tridium Niagara Enterprise Security 2.3u1, all versions prior to 2.3.118.6, Niagara AX 3.8u4, all versions prior to 3.8.401.1, Niagara 4.4u2, all versions prior to 4.4.93.40.2, and Niagara 4.6, all versions prior to 4.6.96.28.4

> Remote attackers can inject malicious scripts into web pages of Tridium Niagara systems, potentially compromising user confidentiality.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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:** 29 Jan 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-76hj-25wr-pvgg

## What is CVE-2018-18985?

CVE-2018-18985 is a medium-severity cross-site scripting vulnerability in Tridium Niagara Enterprise Security 2.3u1, all versions prior to 2.3.118.6, Niagara AX 3.8u4, all versions prior to 3.8.401.1, Niagara 4.4u2, all versions prior to 4.4.93.40.2, and Niagara 4.6, all versions prior to 4.6.96.28.4, published on 29 Jan 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Tridium Niagara Enterprise Security 2.3u1, all versions prior to 2.3.118.6, Niagara AX 3.8u4, all versions prior to 3.8.401.1, Niagara 4.4u2, all versions prior to 4.4.93.40.2, and Niagara 4.6, all versions prior to 4.6.96.28.4 a cross-site scripting vulnerability has been identified that may allow a remote attacker to inject code to some web pages affecting confidentiality.

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

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

It affects 3 products.


Products: Tridium Niagara, Tridium Niagara Ax Framework, Tridium Niagara Enterprise Security.

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

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

## Is CVE-2018-18985 being exploited?

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

## Other vulnerabilities in Tridium Niagara Enterprise Security 2.3u1, all versions prior to 2.3.118.6, Niagara AX 3.8u4, all versions prior to 3.8.401.1, Niagara 4.4u2, all versions prior to 4.4.93.40.2, and Niagara 4.6, all versions prior to 4.6.96.28.4

- [CVE-2017-16748](https://insights.sbomify.com/CVE-2017-16748/): An attacker can log into the local Niagara platform (Niagara AX Framework Versions 3.8 and prior or Niagara 4 Framework Versions 4.4 and pri (critical 9.8)
- [CVE-2025-3937](https://insights.sbomify.com/CVE-2025-3937/): Use of Password Hash with Insufficient Computational Effort (high 7.7)
- [CVE-2025-3944](https://insights.sbomify.com/CVE-2025-3944/): Incorrect Permission Assignment for Critical Resource (high 7.2)
- [CVE-2025-3945](https://insights.sbomify.com/CVE-2025-3945/): Improper Neutralization of Argument Delimiters in a Command (‘Argument Injection’) (high 7.2)
- [CVE-2017-16744](https://insights.sbomify.com/CVE-2017-16744/): Path traversal in Niagara AX Framework and Niagara 4 Framework (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18985 is a medium-severity cross-site scripting vulnerability in Tridium Niagara Enterprise Security 2.3u1, all versions prior to 2.3.118.6, Niagara AX 3.8u4, all versions prior to 3.8.401.1, Niagara 4.4u2, all versions prior to 4.4.93.40.2, and Niagara 4.6, all versions prior to 4.6.96.28.4, published on 29 Jan 2019. 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-18985 in the wild and no public exploit code.

Affected product: Tridium Niagara Enterprise Security 2.3u1, all versions prior to 2.3.118.6, Niagara AX 3.8u4, all versions prior to 3.8.401.1, Niagara 4.4u2, all versions prior to 4.4.93.40.2, and Niagara 4.6, all versions prior to 4.6.96.28.4. 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-18985/ (Markdown: https://insights.sbomify.com/CVE-2018-18985/index.md)
```

## Sources

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

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