Is CVE-2026-119699 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-119699 being exploited in the wild.

How severe is CVE-2026-119699?

Medium severity, with a CVSS score of 5.3, published 30 October 2026.

Which products and versions are affected?

WPGraphQL Smart Cache before 2.3.3.

Is there a fix for CVE-2026-119699?

Yes: fixed in 2.3.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-119699 attacked?

It is attacked over the network.

Am I affected by CVE-2026-119699?

Check whether you run WPGraphQL Smart Cache 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.

CVE-2026-119699: WPGraphQL Smart Cache uncontrolled resource consumption

CVE-2026-119699 · Severity: medium · CVSS 5.3 · Published 2026-10-30

WPGraphQL Smart Cache is a WordPress plugin that optimizes GraphQL query performance through caching. An unauthenticated attacker can exploit a flaw in the Automatic Persisted Query handler to create unlimited query documents in the database, causing the WordPress database to grow without bound and degrade performance. This could lead to database outages and service disruption for WordPress sites using this plugin.

Vendors: WPGraphQL.

Quick answers

Is CVE-2026-119699 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-119699 being exploited in the wild.
How severe is CVE-2026-119699?: Medium severity, with a CVSS score of 5.3, published 30 October 2026.
Which products and versions are affected?: WPGraphQL Smart Cache before 2.3.3.
Is there a fix for CVE-2026-119699?: Yes: fixed in 2.3.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-119699 attacked?: It is attacked over the network.
Am I affected by CVE-2026-119699?: Check whether you run WPGraphQL Smart Cache 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

Fixed in: 2.3.3

Technical details

The vulnerability exists in the Automatic Persisted Query handler before version 2.3.3, which stores query documents by their SHA-256 hash without validation of uniqueness or limits. An attacker can send distinct GraphQL queries with matching queryId values or send batched operations to cause unlimited entries to be persisted in the wp_posts table. This uncontrolled resource consumption can exhaust database storage and degrade performance.

Affected products

WPGraphQL Smart Cache before 2.3.3

Timeline

2026-10-30: disclosed

References

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