# CVE-2019-6016: Cross-site scripting in REMISE Payment Module (2.11, 2.12 and 2.13)

> Remote attackers can inject arbitrary web script or HTML into the REMISE Payment Module, potentially compromising user sessions or data.

- **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 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vrc5-rf39-g54c

## What is CVE-2019-6016?

CVE-2019-6016 is a medium-severity cross-site scripting vulnerability in REMISE Payment Module (2.11, 2.12 and 2.13), published on 26 Dec 2019. 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

Cross-site scripting vulnerability in REMISE Payment Module (2.11, 2.12 and 2.13) version 3.0.12 and earlier allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

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

## Which versions are affected by CVE-2019-6016?

It affects 1 product.


Products: Remise Payment Module.

## How do I fix CVE-2019-6016?

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

## Is CVE-2019-6016 being exploited?

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

## Other vulnerabilities in REMISE Payment Module (2.11, 2.12 and 2.13)

- [CVE-2019-6017](https://insights.sbomify.com/CVE-2019-6017/): Information disclosure in REMISE Payment Module (2.11, 2.12 and 2.13) (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6016 and fix it if it is affected.

What it is: CVE-2019-6016 is a medium-severity cross-site scripting vulnerability in REMISE Payment Module (2.11, 2.12 and 2.13), published on 26 Dec 2019. 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-2019-6016 in the wild and no public exploit code.

Affected product: REMISE Payment Module (2.11, 2.12 and 2.13). 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-2019-6016/ (Markdown: https://insights.sbomify.com/CVE-2019-6016/index.md)
```

## Sources

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

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