CVE-2016-9126: XSS
First published: Tue Mar 28 2017(Updated: )
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.
Credit: support@hackerone.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Revive Adserver | <=3.2.2 |
Remedy
https://github.com/revive-adserver/revive-adserver/commit/8d8c6df309ff5fde9dd4770abcd4ec5d2449b3ec
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-9126?
CVE-2016-9126 has a medium severity rating due to its potential for persistent XSS attacks.
How do I fix CVE-2016-9126?
To fix CVE-2016-9126, upgrade to Revive Adserver version 3.2.3 or later.
Who is affected by CVE-2016-9126?
CVE-2016-9126 affects all users of Revive Adserver versions prior to 3.2.3.
What type of vulnerability is CVE-2016-9126?
CVE-2016-9126 is a persistent cross-site scripting (XSS) vulnerability.
Can CVE-2016-9126 be exploited by regular users?
Yes, CVE-2016-9126 can be exploited by authenticated users with sufficient privileges to create other users.
- agent/type
- agent/remedy
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/author
- agent/severity
- agent/references
- agent/weakness
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/revive-adserver
- canonical/revive adserver
- version/revive adserver/3.2.2