CVE-2021-22872 json
Revive Adserver before 5.1.0 is vulnerable to a reflected cross-site scripting (XSS) vulnerability via the publicly accessible afr.php deli…
published 2021-01-21 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-10007
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
Revive Adserver before 5.1.0 is vulnerable to a reflected cross-site scripting (XSS) vulnerability via the publicly accessible afr.php delivery script. While this issue was previously addressed in modern browsers as CVE-2020-8115, some older browsers (e.g., IE10) that do not automatically URL encode parameters were still vulnerable.
Patch / fix
- revive-adserver revive_adserver 5.1.0
Exploit prediction
3.49% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- hackerone.com https://hackerone.com/reports/986365 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Affected products
- n/a https://github.com/revive-adserver/revive-adserver
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/revive-adserver/revive-adserver/commit/00fdb8d0e
patch, third-party-advisory
-
github.com
/revive-adserver/revive-adserver/commit/1dbcf7d50
patch, third-party-advisory
-
hackerone.com
/reports/986365
exploit, third-party-advisory
-
revive-adserver.com
/security/revive-sa-2021-001/
vendor-advisory
-
seclists.org
/fulldisclosure/2021/Jan/60
mailing-list, broken-link, third-party-advisory
-
packetstormsecurity.com
/files/161070/Revive-Adserver-5.0.5-Cross-Site-Scripting-Open-Redirect.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2021-22872
- NVD CVE-2021-22872
Fencer Vulns 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.