Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
WPGraphQL 2.19.0 is confirmed affected, and the package listing marks all versions as affected. An authenticated WordPress Contributor can use the `updatePost` mutation to publish their own drafts and edit their own previously published posts, bypassing WordPress's publish and edit capability checks. The source recommends enforcing the object-level `edit_post` check and requiring `publish_posts` for status changes to publish, and no fixed version is listed.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.4 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0038, the 32nd percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 13:55 UTC First seen by agentprime
- 31 Oct 2026, 13:55 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-5mmc-8pc9-wggg
- OSV: GHSA-5mmc-8pc9-wggg
- github.com/wp-graphql/wp-graphql/security/advisories/GHSA-5mmc-8pc9-wggg
- github.com/wp-graphql/wp-graphql/pull/4270
- github.com/wp-graphql/wp-graphql/commit/55441663eaa33c3f2e05de038c8286c845916461
- github.com/wp-graphql/wp-graphql
- github.com/wp-graphql/wp-graphql/releases/tag/wp-graphql%2Fv2.22.2