CVE-2016-9130: XSS
First published: Tue Mar 28 2017(Updated: )
Revive Adserver before 3.2.3 suffers from Persistent XSS. A vector for persistent XSS attacks via the Revive Adserver user interface exists, requiring a trusted (non-admin) account. The website name wasn't properly escaped when displayed in the campaign-zone.php script.
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/f6880330a8e11e804663f132867e9eb9b1f94e83
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-9130?
The severity of CVE-2016-9130 is classified as medium due to its potential for persistent XSS attacks.
How do I fix CVE-2016-9130?
To fix CVE-2016-9130, upgrade to Revive Adserver version 3.2.3 or later, where the vulnerability has been addressed.
What is the impact of CVE-2016-9130?
The impact of CVE-2016-9130 allows attackers to execute scripts in the context of a victim's browser via stored XSS.
Who is affected by CVE-2016-9130?
Users of Revive Adserver versions prior to 3.2.3 with non-admin accounts are affected by CVE-2016-9130.
What kind of vulnerabilities are related to CVE-2016-9130?
CVE-2016-9130 is related to persistent cross-site scripting (XSS) vulnerabilities in web applications.
- agent/references
- agent/type
- agent/remedy
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/author
- agent/severity
- 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