# CVE-2026-119700: WPGraphQL before 2.24.2 Object Existence Disclosure via Media and Comment Mutations


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-r7m4-3v6c-3435, GHSA-rgvw-jqg8-92x3

## What is CVE-2026-119700?

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

### Official description

WPGraphQL before 2.24.2 contains an information disclosure vulnerability that allows unauthenticated attackers to determine object existence through distinct error responses. Attackers can iterate IDs against deleteMediaItem, updateMediaItem, deleteComment and updateComment mutations to discover hidden draft, private, trashed posts, custom post types, and unapproved comments.

Weakness: CWE-204 (Observable Response Discrepancy)

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


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

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

## Is CVE-2026-119700 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119700 is a medium-severity vulnerability in WPGraphQL, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119700 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-119700/ (Markdown: https://insights.sbomify.com/CVE-2026-119700/index.md)
```

## Sources

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

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