# CVE-2023-4959: Quay: cross-site request forgery (csrf) on config-editor page

> Attackers can force users to reconfigure the Quay instance, potentially adding admin users, via CSRF on the config-editor page.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **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:** 15 Sep 2023
- **Updated:** 7 Nov 2025
- **Also known as:** GHSA-xphq-2g8c-mfh6

## What is CVE-2023-4959?

CVE-2023-4959 is a medium-severity vulnerability in Red Hat Quay 3, published on 15 Sep 2023. 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

A flaw was found in Quay. Cross-site request forgery (CSRF) attacks force a user to perform unwanted actions in an application. During the pentest, it was detected that the config-editor page is vulnerable to CSRF. The config-editor page is used to configure the Quay instance. By coercing the victim’s browser into sending an attacker-controlled request from another domain, it is possible to reconfigure the Quay instance (including adding users with admin privileges).

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

## Which versions are affected by CVE-2023-4959?

It affects 1 product.


Products: Redhat Quay.

## How do I fix CVE-2023-4959?

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

## Is CVE-2023-4959 being exploited?

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

## Other vulnerabilities in Red Hat Quay 3

- [CVE-2020-27832](https://insights.sbomify.com/CVE-2020-27832/): Cross-site scripting in quay (critical 9.0)
- [CVE-2025-4374](https://insights.sbomify.com/CVE-2025-4374/): Quay: incorrect privilege assignment (medium 6.5)
- [CVE-2023-4956](https://insights.sbomify.com/CVE-2023-4956/): Quay: clickjacking on config-editor page severity (medium 6.5)
- [CVE-2019-10205](https://insights.sbomify.com/CVE-2019-10205/): Information disclosure in quay (medium 6.0)
- [CVE-2026-6848](https://insights.sbomify.com/CVE-2026-6848/): Quay: red hat quay: authentication bypass allows privileged actions without valid credentials (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4959 and fix it if it is affected.

What it is: CVE-2023-4959 is a medium-severity vulnerability in Red Hat Quay 3, published on 15 Sep 2023. 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-2023-4959 in the wild and no public exploit code.

Affected product: Red Hat Quay 3. 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-2023-4959/ (Markdown: https://insights.sbomify.com/CVE-2023-4959/index.md)
```

## Sources

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

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