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