Vulnerability Description
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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Revive-Adserver | Revive Adserver | <= 3.2.2 |
Related Weaknesses (CWE)
References
- https://github.com/revive-adserver/revive-adserver/commit/f6880330a8e11e804663f1Issue TrackingPatchThird Party Advisory
- https://www.revive-adserver.com/security/revive-sa-2016-001/PatchVendor Advisory
- https://github.com/revive-adserver/revive-adserver/commit/f6880330a8e11e804663f1Issue TrackingPatchThird Party Advisory
- https://www.revive-adserver.com/security/revive-sa-2016-001/PatchVendor Advisory
FAQ
What is CVE-2016-9130?
CVE-2016-9130 is a vulnerability with a CVSS score of 5.4 (MEDIUM). 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 w...
How severe is CVE-2016-9130?
CVE-2016-9130 has been rated MEDIUM with a CVSS base score of 5.4/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2016-9130?
Check the references section above for vendor advisories and patch information. Affected products include: Revive-Adserver Revive Adserver.