# CVE-2022-51020: Flower before 2.2.0 CSRF via Worker and Task Control API Endpoints

> Attackers can force authenticated users to shut down Celery workers or revoke tasks via CSRF in Flower monitoring tool.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:H/SC:N/SI:N/SA: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:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-xg8m-6cg7-cmf8

## What is CVE-2022-51020?

CVE-2022-51020 is a medium-severity vulnerability in mher flower, published on 12 Oct 2026. 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 before 2.2.0 contains a cross-site request forgery vulnerability because Tornado xsrf_cookies is disabled and the OAuth session cookie lacks SameSite. Attackers can lure authenticated users to malicious pages that POST to /api/worker/shutdown, /api/worker/pool/restart, or /api/task/revoke to shut down Celery workers, resize pools, and revoke tasks.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-51020?


## How do I fix CVE-2022-51020?

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

## Is CVE-2022-51020 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-51020 and fix it if it is affected.

What it is: CVE-2022-51020 is a medium-severity vulnerability in mher flower, published on 12 Oct 2026. 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-2022-51020 in the wild and no public exploit code.

Affected product: mher flower. 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-2022-51020/ (Markdown: https://insights.sbomify.com/CVE-2022-51020/index.md)
```

## Sources

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

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