CVE-2025-31481: GraphQL query operations security can be bypassed

CVE-2025-31481 · Severity: low · CVSS 3.1 · Published 2025-04-04

GraphQL query operations security can be bypassed

Technologies: api-platform/core (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2025-31481 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-31481 being exploited in the wild.
How severe is CVE-2025-31481?
Low severity, with a CVSS score of 3.1, published 4 April 2025.
Which products and versions are affected?
api-platform/core (Packagist) ECOSYSTEM:introduced=4.0.0-alpha.1,fixed=4.0.22; api-platform/graphql (Packagist) ECOSYSTEM:introduced=4.0.0-alpha.1,fixed=4.0.22.
Is there a fix for CVE-2025-31481?
Yes. api-platform/core (Packagist): upgrade to 4.0.22 or later; api-platform/graphql (Packagist): upgrade to 4.0.22 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-31481?
Check whether you run api-platform/core (Packagist) or api-platform/graphql (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • api-platform/core (Packagist): upgrade to 4.0.22 or later
    composer require api-platform/core:^4.0.22
  • api-platform/graphql (Packagist): upgrade to 4.0.22 or later
    composer require api-platform/graphql:^4.0.22

Affected products

  • api-platform/core (Packagist) ECOSYSTEM:introduced=4.0.0-alpha.1,fixed=4.0.22
  • api-platform/graphql (Packagist) ECOSYSTEM:introduced=4.0.0-alpha.1,fixed=4.0.22

Identifiers

  • CVE-2025-31481
  • GHSA-cg3c-245w-728m

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.