# CVE-2018-20663: The Reporting Addon for CUBA Platform has Persistent XSS

> Persistent XSS in CUBA Platform Reporting Addon allows attackers to inject scripts via the report name field, potentially compromising user sessions.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Jan 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rff7-964g-pppx

## What is CVE-2018-20663?

CVE-2018-20663 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Jan 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Reporting Addon (aka Reports Addon) through 2019-01-02 for CUBA Platform through 6.10.x has Persistent XSS via the "Reports > Reports" name field.

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

## Which versions are affected by CVE-2018-20663?

6 open source packages ship an affected version, including com.haulmont.cuba:cuba-web-toolkit. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.haulmont.cuba:cuba-web-toolkit` | Maven | All versions | 6.8.15 |
| `com.haulmont.cuba:cuba-web-toolkit` | Maven | All versions | 6.8.15 |
| `com.haulmont.cuba:cuba-web-toolkit` | Maven | From 6.10.0 | 6.10.7 |
| `com.haulmont.cuba:cuba-web-toolkit` | Maven | From 6.10.0 | 6.10.7 |
| `com.haulmont.cuba:cuba-web-toolkit` | Maven | From 6.9.0 | 6.9.8 |
| `com.haulmont.cuba:cuba-web-toolkit` | Maven | From 6.9.0 | 6.9.8 |

Products: Haulmont Cuba Platform, Haulmont Reporting.

## How do I fix CVE-2018-20663?

Upgrade com.haulmont.cuba:cuba-web-toolkit to a fixed version for your release line: 6.8.15, 6.10.7 or 6.9.8.

## Is CVE-2018-20663 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-32952](https://insights.sbomify.com/CVE-2025-32952/): io.jmix.localfs:jmix-localfs affected by DoS in the Local File Storage (medium 6.5)
- [CVE-2025-32951](https://insights.sbomify.com/CVE-2025-32951/): io.jmix.rest:jmix-rest allows XSS in the /files Endpoint of the Generic REST API (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20663 and fix it if it is affected.

What it is: CVE-2018-20663 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Jan 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-20663 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.haulmont.cuba:cuba-web-toolkit (Maven): affected all versions; fixed in 6.8.15
- com.haulmont.cuba:cuba-web-toolkit (Maven): affected all versions; fixed in 6.8.15
- com.haulmont.cuba:cuba-web-toolkit (Maven): affected from 6.10.0; fixed in 6.10.7
- com.haulmont.cuba:cuba-web-toolkit (Maven): affected from 6.10.0; fixed in 6.10.7
- com.haulmont.cuba:cuba-web-toolkit (Maven): affected from 6.9.0; fixed in 6.9.8
- com.haulmont.cuba:cuba-web-toolkit (Maven): affected from 6.9.0; fixed in 6.9.8

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

## Sources

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

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