# CVE-2021-28079: Cross-site scripting in n/a

> An attacker can execute arbitrary code by tricking a victim into opening a malicious Jamovi document containing an XSS payload.

- **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:** 26 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9qg2-48rp-q2cr

## What is CVE-2021-28079?

CVE-2021-28079 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Apr 2021. 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

Jamovi <=1.6.18 is affected by a cross-site scripting (XSS) vulnerability. The column-name is vulnerable to XSS in the ElectronJS Framework. An attacker can make a .omv (Jamovi) document containing a payload. When opened by victim, the payload is triggered.

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

## Which versions are affected by CVE-2021-28079?

It affects 1 product.


Products: Jamovi Jamovi.

## How do I fix CVE-2021-28079?

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

## Is CVE-2021-28079 being exploited?

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

Public exploit code:

- POC Jamovi <=1.6.18 is affected by a cross-site scripting (XSS) vulnerability. The column-name is vulnerable to XSS in the ElectronJS Framework. An attacker can make a .omv (Jamovi) document containing a payload. When opened by victim, the payload is triggered. (github_poc): https://github.com/g33xter/CVE-2021-28079

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-28079 and fix it if it is affected.

What it is: CVE-2021-28079 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Apr 2021. 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-2021-28079 in the wild and no public exploit code.

Affected product: n/a. 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-2021-28079/ (Markdown: https://insights.sbomify.com/CVE-2021-28079/index.md)
```

## Sources

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

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