← back
CVE-2025-23204mediumCWE-20

GraphQl securityAfterResolver not called

13Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 4.4epss 0.3%
exploitation probability
0.3%top 80% of all CVEs
observed exploitation
nono source reports it
In short

A security check in GraphQL APIs is being skipped due to a missing break statement, allowing requests that should be denied to pass through when certain security conditions are set.

Technical detail

A control flow vulnerability in API Platform Core (v3.3.8+) causes the securityAfterResolver check to be overwritten without a break statement in a switch/conditional clause. This impacts authorization enforcement only when security rules are defined exclusively in the afterResolver hook without corresponding security constraints in the main security layer, potentially allowing unauthorized access to protected resolvers.

Summary generated and translated by AI from the official description.
API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. Starting in version 3.3.8, a security check that gets called after GraphQl resolvers is always replaced by another one as there's no break in a clause. As this falls back to `security`, the impact is there only when there's only a security after resolver and none inside security. Version 3.3.15 contains a patch for the issue.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
Affected products
api-platform · core