# CVE-2019-16926: Cross-site scripting in n/a

> Cross-site scripting vulnerability in Flower via crafted worker name, though disputed by the author as requiring privileged 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:** 27 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rvm9-vjh6-7fhr

## What is CVE-2019-16926?

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

Flower 0.9.3 has XSS via a crafted worker name. NOTE: The project author stated that he doesn't think this is a valid vulnerability. Worker name and task name aren’t user facing configuration options. They are internal backend config options and person having rights to change them already has full access

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

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

It affects 1 product.


Products: Flower Project Flower.

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

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

## Is CVE-2019-16926 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-30034](https://insights.sbomify.com/CVE-2022-30034/): Flower OAuth authentication bypass (high 8.6)
- [CVE-2019-16925](https://insights.sbomify.com/CVE-2019-16925/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16926 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Sep 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-16926 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-2019-16926/ (Markdown: https://insights.sbomify.com/CVE-2019-16926/index.md)
```

## Sources

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

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