# CVE-2026-119702: WPGraphQL before 2.24.1 Missing Authorization via createComment Mutation


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-4vgv-vvxr-9fh9, GHSA-wj7h-xjr7-93c6

## What is CVE-2026-119702?

CVE-2026-119702 is a medium-severity vulnerability in WPGraphQL, published on 30 Oct 2026. 

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-119702?


## How do I fix CVE-2026-119702?

No fix has been published for CVE-2026-119702 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119702 being exploited?

There is no known exploitation of CVE-2026-119702 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119702 and fix it if it is affected.

What it is: CVE-2026-119702 is a medium-severity vulnerability in WPGraphQL, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119702 in the wild and no public exploit code.

Affected product: WPGraphQL. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119702/ (Markdown: https://insights.sbomify.com/CVE-2026-119702/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119702
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119702
- OSV: https://osv.dev/vulnerability/CVE-2026-119702

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119702/
Summaries are generated and may contain mistakes; the official description above is the record.