CVE-2016-9454 json
Revive Adserver before 3.2.3 suffers from Persistent XSS.
published 2017-03-28 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-10260
- cvss
- 5.4
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
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 banner image URL for external banners wasn't properly escaped when displayed in most of the banner related pages.
Patch / fix
Exploit prediction
1.10% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.4 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Affected products
- n/a Revive Adserver All versions before 3.2.3
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/revive-adserver/revive-adserver/commit/f6880330a8e11e804663f132867e9eb9b1f94e83
issue-tracking, patch, third-party-advisory
-
revive-adserver.com
/security/revive-sa-2016-001/
patch, vendor-advisory
-
securityfocus.com
/bid/83964
vdb-entry
Sources
- CVE List CVE-2016-9454
- NVD CVE-2016-9454
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.