# CVE-2022-39322: @keystone-6/core vulnerable to field-level access-control bypass for multiselect field

> Attackers can bypass field-level access controls on multiselect fields in Keystone 6, potentially reading or modifying restricted data.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Oct 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-6mhr-52mv-6v6f

## What is CVE-2022-39322?

CVE-2022-39322 is a critical missing authorization vulnerability in keystonejs keystone, published on 25 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

@keystone-6/core is a core package for Keystone 6, a content management system for Node.js. Starting with version 2.2.0 and prior to version 2.3.1, users who expected their `multiselect` fields to use the field-level access control - if configured - are vulnerable to their field-level access control not being used. List-level access control is not affected. Field-level access control for fields other than `multiselect` are not affected. Version 2.3.1 contains a fix for this issue. As a workaround, stop using the `multiselect` field.

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

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

2 open source packages ship an affected version, including @keystone-6/core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@keystone-6/core` | npm | From 2.2.0 | 2.3.1 |
| `@keystone-6/core` | npm | From 2.2.0 | 2.3.1 |

Products: Keystonejs Keystone.

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

Upgrade @keystone-6/core to 2.3.1 or later.

## Is CVE-2022-39322 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39322 exists.

## Other vulnerabilities in keystonejs keystone

- [CVE-2022-39382](https://insights.sbomify.com/CVE-2022-39382/): NODE_ENV in Keystone defaults to development with esbuild (critical 9.8)
- [CVE-2022-29354](https://insights.sbomify.com/CVE-2022-29354/): File upload in n/a (critical 9.8)
- [CVE-2017-16570](https://insights.sbomify.com/CVE-2017-16570/): Cross-Site Request Forgery (CSRF) in keystone (high 8.8)
- [CVE-2017-15879](https://insights.sbomify.com/CVE-2017-15879/): Keystone is vulnerable to CSV injection (high 8.8)
- [CVE-2015-9240](https://insights.sbomify.com/CVE-2015-9240/): Authentication Weakness in keystone (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39322 is a critical missing authorization vulnerability in keystonejs keystone, published on 25 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39322 exists.

Affected packages and fixed versions:
- @keystone-6/core (npm): affected from 2.2.0; fixed in 2.3.1
- @keystone-6/core (npm): affected from 2.2.0; fixed in 2.3.1

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-39322/ (Markdown: https://insights.sbomify.com/CVE-2022-39322/index.md)
```

## Sources

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

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