Stored XSS in Revive Adserver Audit Log via Malicious Username
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Revive | Adserver | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Revive | Adserver |
|
No CVSS v4.0
No CVSS v3.1
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.389% probability within 30 days)
| Link | Providers |
|---|---|
| https://hackerone.com/reports/3680090 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Stored XSS in Revive Adserver Audit Log via Malicious Username |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Stored XSS via Username in Revive Adserver Audit Log |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Stored XSS via Username in Revive Adserver Audit Log |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Stored Cross‑Site Scripting in Revive Adserver Audit Log via Username Field |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Stored Cross‑Site Scripting in Revive Adserver Audit Log via Username Field |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Revive
Revive adserver |
|
| Vendors & Products |
Revive
Revive adserver |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A stored XSS can be exploited by leveraging the usernames as an attack vector. When an admin user viewed the audit log details for affected entries, any malicious JavaScript payload embedded in the username would be executed due to missing output sanitisation. Proper escaping has been added to the audit log details output. | |
| Weaknesses | CWE-79 | |
| References |
| |
| Metrics |
cvssV3_0
|