Answer in brief
CVE-2026-88974 records a Medium severity (CVSS 5.4) vulnerability in WPGraphQL: Contributor can publish and modify posts without the required capabilities via updatePost. The current sources do not mark it as known exploited. The current feed maps wp-graphql/wp-graphql (composer), wp-graphql/wp-graphql (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps wp-graphql/wp-graphql (composer), wp-graphql/wp-graphql (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| wp-graphql/wp-graphqlcomposer | <2.22.2 | Not reported |
| wp-graphql/wp-graphqlgeneric | <2.22.2 | 2.22.2 |
Published upstream
Sep 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 23, 2026
WPGraphQL provides a GraphQL API for WordPress sites. Prior to 2.22.2, the updatePost mutation in src/Mutation/PostObjectUpdate.php checks only the collection-level edit_posts capability and the post author, but does not enforce the object-level edit_post capability or require publish_posts for public status transitions. An authenticated Contributor can therefore publish the Contributor's own draft without editorial approval or modify the Contributor's previously published post despite lacking edit_published_posts, while posts owned by other authors remain protected. This issue is fixed in version 2.22.2.
Quoted source text, attributed separately from HOL analysis.