CVE-2019-1000011

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.

Published: 2019-02-04 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-1000011 is rated Moderate Risk (47.5/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.02%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-1000011

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.16% 1.02% +0.86%
2 2025-12-02 0.26% 0.16% -0.10%
3 2025-11-21 — 0.26% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-1000011

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 3.6 [email protected]
5.5 2.0 MEDIUM
AV:N/AC:L/Au:S/C:N/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.0 4.9 [email protected]

Weakness enumeration for CVE-2019-1000011

GitHub Security Advisory for CVE-2019-1000011

GHSA-974j-wjxx-wggj · Severity: medium · Ecosystem: composer — Incorrect Access Control vulnerability in api-platform/core

Affected software / configurations for CVE-2019-1000011

Vendor Product Version Raw CPE
api-platform core >= 2.2.0, <= 2.3.5 cpe:2.3:a:api-platform:core:*:*:*:*:*:*:*:*

References for CVE-2019-1000011

URL Tags
https://github.com/api-platform/core/issues/2364 Issue Tracking Third Party Advisory
https://github.com/api-platform/core/pull/2441 Issue Tracking Third Party Advisory
cvelogic Threat Intelligence