Read the docs

WPGraphQL createComment lets attackers comment on hidden posts

Priority LOW 36CWE-862Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-862.

Summary

WPGraphQL before 2.24.1 has a missing authorization flaw in its createComment mutation (CWE-862). An unauthenticated remote attacker can attach comments to draft, private, trashed, or password-protected posts by bypassing post status checks. This lets attackers leak hidden post titles through moderator notifications, enumerate post IDs, and backdate comments or mark them as pingbacks.

Written with Claude Haiku 5.5 from the sources below · 2026-10-30

Description from the CNA

WPGraphQL before 2.24.1 contains a missing authorization vulnerability in the createComment mutation that allows unauthenticated attackers to comment on non-public posts by bypassing post status checks. Attackers can attach comments to draft, private, trashed, or password-protected posts to leak hidden titles via moderator notifications, enumerate post IDs, and backdate comments or mark them as pingbacks.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00361 30th percentileScored 2026-11-07
Fix Fixed WPGraphQL (WPGraphQL): 2.24.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
WPGraphQLWPGraphQLbefore 2.24.12.24.1Patch availableCNA
  • WPGraphQL VendorWPGraphQL Affected before 2.24.1 Fixed in 2.24.1 Patch available CNA

Remediation

Update WPGraphQL to version 2.24.1, which fixes the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-10-30

  • Fix · CNA WPGraphQL (WPGraphQL) Fixed in 2.24.1

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    WPGraphQL 2.24.1

    2 records Highest priority Priority LOW 2 LOW

    Other records, highest priority first

    • TI-2026-83176 Email flooding in WPGraphQL via aliased password reset mutationsPriority LOW 37

Timeline

  1. 2026-10-30 Threatist record created from CVE-2026-119702
  2. 2026-10-30 CISA SSVC decision points changed
  3. 2026-10-30 Priority changed: MEDIUM → LOW
  4. 2026-10-30 Alias added: GHSA-wj7h-xjr7-93c6

References

  • TI-2021-22572 WordPress Plugin WPGraphQL 1.3.5 Denial of Service CVSS 4.0HIGH 8.7
  • TI-2026-39574 WPGraphQL has deprecated `user` field on SendPasswordResetEmailPayload that leaks user… CVSS 4.0MEDIUM 6.9
  • TI-2026-22282 WPGraphQL Repo Vulnerable to Command Injection via Unsanitized GitHub Actions Expression in Release Workflow CVSS 3.1HIGH 7.7
  • TI-2026-60306 WPGraphQL: Contributor can publish and modify posts without the required capabilities via updatePost CVSS 3.1MEDIUM 5.4
  • TI-2026-25701 Missing authorization in WPGraphQL wp-graphql CVSS 3.1MEDIUM 4.3
  • TI-2026-83176 Email flooding in WPGraphQL via aliased password reset mutations CVSS 4.0MEDIUM 6.9
See all 13 →

Sources