# CVE-2026-119702: WPGraphQL createComment mutation missing authorization

Source: https://junglewise.ai/threats/cve-2026-119702-wpgraphql-before-2-24-1-contains-a-missing-authorization  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-30. Updated: 2026-10-30  
License: CC BY 4.0 with a link back

CVE-2026-119702 · Severity: medium · CVSS 6.5 · Published 2026-10-30

WPGraphQL is a WordPress plugin that exposes WordPress functionality through a GraphQL API. The createComment mutation fails to properly validate whether an unauthenticated attacker has permission to comment on posts, allowing them to attach comments to draft, private, or password-protected posts that should be hidden. An attacker can exploit this to leak post titles through moderator notifications, enumerate internal post IDs, or manipulate comment metadata.

Technologies: [WPGraphQL](https://junglewise.ai/threats/technologies/wpgraphql). Vendors: [WPGraphQL](https://junglewise.ai/threats/vendors/wpgraphql).

## Quick answers

**Is CVE-2026-119702 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-119702 being exploited in the wild.

**How severe is CVE-2026-119702?** Medium severity, with a CVSS score of 6.5, published 30 October 2026.

**Which products and versions are affected?** WPGraphQL before 2.24.1.

**Is there a fix for CVE-2026-119702?** Yes: fixed in 2.24.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-119702 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-119702?** Check whether you run WPGraphQL 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.24.1

## Technical details

The createComment mutation in WPGraphQL before version 2.24.1 lacks authorization checks on post status before allowing comments to be created. Unauthenticated attackers can bypass post visibility restrictions (draft, private, trash, password-protected) via GraphQL queries. The vulnerability enables information disclosure through moderator notifications, post ID enumeration, and arbitrary comment property manipulation including backdating and status spoofing.

## Affected products

- WPGraphQL WPGraphQL before 2.24.1

## Timeline

- 2026-10-30: disclosed

## References

- [https://github.com/wp-graphql/wp-graphql](https://github.com/wp-graphql/wp-graphql)
- [https://github.com/wp-graphql/wp-graphql/blob/wp-graphql/v2.24.0/plugins/wp-graphql/src/Mutation/CommentCreate.php](https://github.com/wp-graphql/wp-graphql/blob/wp-graphql/v2.24.0/plugins/wp-graphql/src/Mutation/CommentCreate.php)

## Related threats

- [WPGraphQL missing rate limiting in password reset email mutation](https://junglewise.ai/threats/cve-2026-119701-wpgraphql-before-2-24-1-contains-a-missing-rate-limiting)
- [WPGraphQL authorization bypass in updatePost mutation](https://junglewise.ai/threats/cve-2026-88974-wpgraphql-authorization-bypass-in-updatepost-mutation)
- [WPGraphQL user enumeration in SendPasswordResetEmail mutation](https://junglewise.ai/threats/cve-2026-54768-wpgraphql-user-enumeration-in-sendpasswordresetemail-mutation)
- [WPGraphQL SQL injection in WordPress plugin](https://junglewise.ai/threats/cve-2026-40762-wpgraphql-sql-injection-in-wordpress-plugin)
- [WPGraphQL WordPress plugin denial of service via batched queries](https://junglewise.ai/threats/cve-2021-47959-wpgraphql-wordpress-plugin-denial-of-service-via-batched-queries)