# CVE-2020-25102: silverstripe-advancedreports vulnerable to XSS

> An attacker can inject malicious JavaScript via SVG documents in the report description field, potentially executing code in the admin interface.

- **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:** 3 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8f2x-hv9r-mh9r

## What is CVE-2020-25102?

CVE-2020-25102 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Sep 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

silverstripe-advancedreports (aka the Advanced Reports module for SilverStripe) 1.0 through 2.0 is vulnerable to Cross-Site Scripting (XSS) because it is possible to inject and store malicious JavaScript code. The affects admin/advanced-reports/DataObjectReport/EditForm/field/DataObjectReport/item (aka report preview) when an SVG document is provided in the Description parameter.

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

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

2 open source packages ship an affected version, including silverstripe-australia/advancedreports. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe-australia/advancedreports` | Packagist | From 1.0 to 2.0 | None |
| `silverstripe-australia/advancedreports` | Packagist | From 1.0 to 2.0 | None |

Products: Advanced Reports Project Advanced Reports.

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

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

## Is CVE-2020-25102 being exploited?

There is no known exploitation of CVE-2020-25102 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25102 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Sep 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: There is no known exploitation of CVE-2020-25102 in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe-australia/advancedreports (Packagist): affected from 1.0 up to 2.0; no fix listed
- silverstripe-australia/advancedreports (Packagist): affected from 1.0 up to 2.0; no fix listed

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-25102/ (Markdown: https://insights.sbomify.com/CVE-2020-25102/index.md)
```

## Sources

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

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