CVE-2019-1000011
Description
API Platform 2.2.0–2.3.5 GraphQL delete mutations allow authorized users to delete any resource due to missing resource class check; fixed in 2.3.6.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
API Platform 2.2.0–2.3.5 GraphQL delete mutations allow authorized users to delete any resource due to missing resource class check; fixed in 2.3.6.
Vulnerability
API Platform versions from 2.2.0 to 2.3.5 contain an incorrect access control vulnerability in GraphQL delete mutations. The ItemMutationResolverFactory fails to verify that the resource class of the provided IRI matches the expected resource class for the mutation. This allows a user authorized to delete a specific resource type (e.g., Office) to delete resources of other types (e.g., Book) by passing a different IRI. The issue was reported in issue #2364 [4] and fixed in pull request #2441 [3].
Exploitation
An attacker must have authorization to perform delete mutations on at least one resource class within the API. The attacker can then craft a GraphQL mutation that invokes a delete mutation for a resource they are authorized to delete but provide the IRI of a different resource class they are not authorized to delete. For example, if authorized to delete Office resources, the attacker can supply the IRI of a Book resource (/api/books/240) in the deleteOffice mutation, resulting in the deletion of the book. No additional privileges or user interaction beyond the authorization are required.
Impact
An authenticated attacker with authorization to delete any resource type can delete arbitrary resources of any class, regardless of their permissions on those specific resource classes. This leads to unauthorized data deletion, potentially causing data loss and service disruption. The confidentiality and integrity of the affected resources are compromised as the attacker can remove data they should not have access to delete.
Mitigation
The vulnerability is fixed in API Platform version 2.3.6 [1][2]. Users running versions 2.2.0 through 2.3.5 should upgrade immediately. For those unable to upgrade, as a workaround, custom input validation can be implemented in mutation resolvers to verify that the resource class of the provided IRI matches the expected class, as demonstrated in the fix [3]. The vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog as of the publication date.
AI Insight generated on May 22, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
api-platform/corePackagist | >= 2.2.0, < 2.2.10 | 2.2.10 |
api-platform/corePackagist | >= 2.3.0, < 2.3.6 | 2.3.6 |
Affected products
2- Range: push, remove, v2.2.0, …
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
5- github.com/advisories/GHSA-974j-wjxx-wggjghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2019-1000011ghsaADVISORY
- github.com/FriendsOfPHP/security-advisories/blob/master/api-platform/core/CVE-2019-1000011.yamlghsaWEB
- github.com/api-platform/core/issues/2364ghsax_refsource_MISCWEB
- github.com/api-platform/core/pull/2441ghsax_refsource_MISCWEB
News mentions
0No linked articles in our index yet.