CVE-2021-22871 json
Revive Adserver before 5.1.0 permits any user with a manager account to store possibly malicious content in the URL website property, which…
published 2021-01-21 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-10006
- cvss
- 4.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
Revive Adserver before 5.1.0 permits any user with a manager account to store possibly malicious content in the URL website property, which is then displayed unsanitized in the affiliate-preview.php tag generation screen, leading to a persistent cross-site scripting (XSS) vulnerability.
Patch / fix
- revive-adserver revive_adserver 5.1.0
Exploit prediction
2.15% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- hackerone.com https://hackerone.com/reports/819362 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/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 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/89b88ce26
patch, third-party-advisory
-
github.com
/revive-adserver/revive-adserver/commit/62a2a0439
patch, third-party-advisory
-
hackerone.com
/reports/819362
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-22871
- NVD CVE-2021-22871
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.