# CVE-2016-9126: Cross-site scripting in Revive Adserver All versions before 3.2.3

> Persistent XSS in Revive Adserver allows authenticated users to hijack administrator accounts via unescaped usernames in the audit trail.

- **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:** 28 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-prj8-5jpv-8374

## What is CVE-2016-9126?

CVE-2016-9126 is a medium-severity cross-site scripting vulnerability in Revive-Adserver Revive Adserver, published on 28 Mar 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Revive Adserver before 3.2.3 suffers from persistent XSS. Usernames are not properly escaped when displayed in the audit trail widget of the dashboard upon login, allowing persistent XSS attacks. An authenticated user with enough privileges to create other users could exploit the vulnerability to access the administrator account.

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

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

It affects 1 product.


Products: Revive-Adserver Revive Adserver.

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

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

## Is CVE-2016-9126 being exploited?

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

## Other vulnerabilities in Revive-Adserver Revive Adserver

- [CVE-2016-9124](https://insights.sbomify.com/CVE-2016-9124/): Security feature bypass in Revive Adserver All versions before 3.2.3 (critical 9.8)
- [CVE-2016-9125](https://insights.sbomify.com/CVE-2016-9125/): Auth bypass in Revive Adserver All versions before 3.2.3 (critical 9.8)
- [CVE-2017-5830](https://insights.sbomify.com/CVE-2017-5830/): Deserialization in n/a (critical 9.8)
- [CVE-2016-9470](https://insights.sbomify.com/CVE-2016-9470/): Other in Revive Adserver All versions before 3.2.5 and 4.0.0 (critical 9.0)
- [CVE-2026-50741](https://insights.sbomify.com/CVE-2026-50741/): Code injection in Adserver (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-9126 is a medium-severity cross-site scripting vulnerability in Revive-Adserver Revive Adserver, published on 28 Mar 2017. 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-2016-9126 in the wild and no public exploit code.

Affected product: Revive-Adserver Revive Adserver. 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-9126/ (Markdown: https://insights.sbomify.com/CVE-2016-9126/index.md)
```

## Sources

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

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