# CVE-2020-8115: Cross-site scripting in https://github.com/revive-adserver/revive-adserver

> Reflected XSS in Revive Adserver allows attackers to execute arbitrary JavaScript, potentially stealing session IDs and gaining admin access.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6qfg-3f8q-4rrv

## What is CVE-2020-8115?

CVE-2020-8115 is a medium-severity cross-site scripting vulnerability in Revive-Adserver Revive Adserver, published on 4 Feb 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A reflected XSS vulnerability has been discovered in the publicly accessible afr.php delivery script of Revive Adserver <= 5.0.3 by Jacopo Tediosi. There are currently no known exploits: the session identifier cannot be accessed as it is stored in an http-only cookie as of v3.2.2. On older versions, however, under specific circumstances, it could be possible to steal the session identifier and gain access to the admin interface. The query string sent to the www/delivery/afr.php script was printed back without proper escaping in a JavaScript context, allowing an attacker to execute arbitrary JS code on the browser of the victim.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2020-8115?

It affects 1 product.


Products: Revive-Adserver Revive Adserver.

## How do I fix CVE-2020-8115?

No fix has been published for CVE-2020-8115 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-8115 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-8115 exists.

Public exploit code:

- Revive Adserver <=5.0.3 - Cross-Site Scripting (nuclei): http/cves/2020/CVE-2020-8115.yaml

## Other vulnerabilities in Revive-Adserver Revive Adserver

- [CVE-2016-9124](https://insights.sbomify.com/CVE-2016-9124/): Security feature bypass in Revive Adserver All versions before 3.2.3 (critical 9.8)
- [CVE-2016-9125](https://insights.sbomify.com/CVE-2016-9125/): Auth bypass in Revive Adserver All versions before 3.2.3 (critical 9.8)
- [CVE-2017-5830](https://insights.sbomify.com/CVE-2017-5830/): Deserialization in n/a (critical 9.8)
- [CVE-2016-9470](https://insights.sbomify.com/CVE-2016-9470/): Other in Revive Adserver All versions before 3.2.5 and 4.0.0 (critical 9.0)
- [CVE-2026-50741](https://insights.sbomify.com/CVE-2026-50741/): Code injection in Adserver (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8115 and fix it if it is affected.

What it is: CVE-2020-8115 is a medium-severity cross-site scripting vulnerability in Revive-Adserver Revive Adserver, published on 4 Feb 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-8115 exists.

Affected product: Revive-Adserver Revive Adserver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-8115/ (Markdown: https://insights.sbomify.com/CVE-2020-8115/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-8115
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-8115
- OSV: https://osv.dev/vulnerability/CVE-2020-8115

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-8115/
Summaries are generated and may contain mistakes; the official description above is the record.