Antoine Bluchet

6 exploits Active since Feb 2023
CVE-2025-31481 WRITEUP HIGH WRITEUP
API Platform Core 3.4.0-3.4.16 and 4.0.0-alpha.1-4.0.21 - Incorrect Authorization via Relay Node Type
API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. Using the Relay special node type you can bypass the configured security on an operation. This vulnerability is fixed in 4.0.22 and 3.4.17.
CVSS 7.5
CVE-2025-31485 WRITEUP HIGH WRITEUP
API Platform Core <4.0.22, <3.4.17 - Info Disclosure
API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. Prior to 4.0.22 and 3.4.17, a GraphQL grant on a property might be cached with different objects. The ApiPlatform\GraphQl\Serializer\ItemNormalizer::isCacheKeySafe() method is meant to prevent the caching but the parent::normalize method that is called afterwards still creates the cache key and causes the issue. This vulnerability is fixed in 4.0.22 and 3.4.17.
CVSS 7.5
CVE-2023-25575 WRITEUP HIGH WRITEUP
API Platform Core 2.7-2.7.9 3.0-3.0.11 - Unauthorized Data Disclosure via Security Rule Caching
API Platform Core is the server component of API Platform: hypermedia and GraphQL APIs. Resource properties secured with the `security` option of the `ApiPlatform\Metadata\ApiProperty` attribute can be disclosed to unauthorized users. The problem affects most serialization formats, including raw JSON, which is enabled by default when installing API Platform. Custom serialization formats may also be impacted. Only collection endpoints are affected by the issue, item endpoints are not. The JSON-LD format is not affected by the issue. The result of the security rule is only executed for the first item of the collection. The result of the rule is then cached and reused for the next items. This bug can leak data to unauthorized users when the rule depends on the value of a property of the item. This bug can also hide properties that should be displayed to authorized users. This issue impacts the 2.7, 3.0 and 3.1 branches. Please upgrade to versions 2.7.10, 3.0.12 or 3.1.3. As a workaround, replace the `cache_key` of the context array of the Serializer inside a custom normalizer that works on objects if the security option of the `ApiPlatform\Metadata\ApiProperty` attribute is used.
CVSS 7.7
CVE-2025-23204 WRITEUP MEDIUM WRITEUP
API Platform Core 3.3.8-3.3.14 - Improper Input Validation in GraphQL Resolver Security Check
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 4.4
CVE-2025-31481 WRITEUP HIGH WRITEUP
API Platform Core 3.4.0-3.4.16 and 4.0.0-alpha.1-4.0.21 - Incorrect Authorization via Relay Node Type
API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. Using the Relay special node type you can bypass the configured security on an operation. This vulnerability is fixed in 4.0.22 and 3.4.17.
CVSS 7.5
CVE-2025-31485 WRITEUP HIGH WRITEUP
API Platform Core <4.0.22, <3.4.17 - Info Disclosure
API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. Prior to 4.0.22 and 3.4.17, a GraphQL grant on a property might be cached with different objects. The ApiPlatform\GraphQl\Serializer\ItemNormalizer::isCacheKeySafe() method is meant to prevent the caching but the parent::normalize method that is called afterwards still creates the cache key and causes the issue. This vulnerability is fixed in 4.0.22 and 3.4.17.
CVSS 7.5