Cross‑site request forgery permits authenticated users to alter tracker data in Revive Adserver 6.0.8 and earlier
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.134% probability within 30 days)
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://hackerone.com/reports/3981932 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Revive
Revive adserver |
|
| Vendors & Products |
Revive
Revive adserver |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Cross‑site request forgery permits authenticated users to alter tracker data in Revive Adserver 6.0.8 and earlier |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A cross-site request forgery vulnerability in tracker-invocation.php in Revive Adserver 6.0.8 and earlier allows an attacker to modify a tracker's name, description or advertiser assignment using an authenticated victim's permissions. A leftover state-changing handler accepts request parameters without verifying a CSRF token, although it is not used by the normal invocation-tag interface. Exploitation requires victim interaction and a request path that carries the victim's session credentials. The issue is fixed in Revive Adserver 6.0.9 by removing the unused tracker-modification handler. | |
| Weaknesses | CWE-352 | |
| References |
| |
| Metrics |
cvssV3_0
|