WPGraphQL 2.22.2 Restores Post Capability Enforcement
Tech GuruQuick Answer
WPGraphQL versions before 2.22.2 are listed as affected by an authorization bypass in updatePost. A Contributor can publish their own draft or change their own published post without the required capabilities. Install the fixed plugin and check whether low-privilege accounts made unexpected changes.
Confirm Scope And Apply The Supported Fix
Next step: Upgrade WPGraphQL to 2.22.2 or a supported release containing the fix. Review post history and role assignments where the endpoint was accessible to Contributors; do not treat a successful update as proof that prior changes were authorized.
Last verified: 2026-09-23 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | WPGraphQL releases before 2.22.2 |
|---|---|
| Advisory | GHSA-5mmc-8pc9-wggg |
| CVE | CVE-2026-88974 |
| Authoritative release date | 2026-09-04 (publication date displayed by the project advisory). |
| Authority revision date | No separate material revision date established in this review; advisory retrieved 2026-10-02. |
| Affected versions | WPGraphQL releases before 2.22.2 |
| Fixed version | WPGraphQL 2.22.2 |
| CVSS base score | 5.4 (CVSS v3.1) |
| CVSS severity | Medium |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The issue is a missing capability check on a GraphQL mutation. Authentication alone is not enough: WordPress must also enforce permission to publish and permission to edit an already published post. The advisory does not establish arbitrary anonymous access to every post.
What To Validate Now
- Inventory. Locate WPGraphQL releases before 2.22.2 deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: WPGraphQL releases before 2.22.2 Do not infer applicability from product family or severity alone.
- Remediate. Apply WPGraphQL 2.22.2 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Use controlled Contributor and Editor accounts with disposable posts in staging. Confirm a Contributor cannot publish a draft or edit a published post through the mutation, while an appropriately authorized account still can. Record both denied and allowed results without exposing account tokens.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
