# CVE-2019-1000011: Incorrect Access Control vulnerability in api-platform/core

> An authenticated user can delete any resource via GraphQL mutations due to incorrect access control checks in API Platform.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Feb 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-974j-wjxx-wggj

## What is CVE-2019-1000011?

CVE-2019-1000011 is a medium-severity missing authorization vulnerability in n/a, published on 4 Feb 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

API Platform version from 2.2.0 to 2.3.5 contains an Incorrect Access Control vulnerability in GraphQL delete mutations that can result in a user authorized to delete a resource can delete any resource. This attack appears to be exploitable via the user must be authorized. This vulnerability appears to have been fixed in 2.3.6.

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

4 open source packages ship an affected version, including api-platform/core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `api-platform/core` | Packagist | From 2.2.0 | 2.2.10 |
| `api-platform/core` | Packagist | From 2.2.0 | 2.2.10 |
| `api-platform/core` | Packagist | From 2.3.0 | 2.3.6 |
| `api-platform/core` | Packagist | From 2.3.0 | 2.3.6 |

Products: Api-Platform Core.

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

Upgrade api-platform/core to a fixed version for your release line: 2.2.10 or 2.3.6.

## Is CVE-2019-1000011 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-25575](https://insights.sbomify.com/CVE-2023-25575/): Secured properties in API Platform Core may be accessible within collections (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-1000011 is a medium-severity missing authorization vulnerability in n/a, published on 4 Feb 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1000011 in the wild and no public exploit code.

Affected packages and fixed versions:
- api-platform/core (Packagist): affected from 2.2.0; fixed in 2.2.10
- api-platform/core (Packagist): affected from 2.2.0; fixed in 2.2.10
- api-platform/core (Packagist): affected from 2.3.0; fixed in 2.3.6
- api-platform/core (Packagist): affected from 2.3.0; fixed in 2.3.6

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

## Sources

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

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