CVE-2016-9126

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account, but needs a user to act. Limited direct impact.

Exploit odds

1.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2017-03-28 02:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:55 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.4% in the next 30 days (EPSS).
• Severity: 5.4 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2017-03-28 02:59 UTC

Last modified

2026-06-17 00:55 UTC

Exploit probability

1.4% · EPSS, next 30 days

Weakness

CWE-79 · Cross-site scripting

Record status

Modified

Affected

• revive-adserver Revive Adserver ≤ 3.2.2

Attack profile CVSS 3.0 · 5.4

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-9126.md and follow it. Check whether this project is affected by CVE-2016-9126. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge