CVE-2026-27938 HIGH

CVE-2026-27938: WPGraphQL Repo Vulnerable to Command Injection via Unsanitized GitHub Actions Expression in Release Workflow

Vendor Wp-Graphql
Product wp-graphql
Weakness CWE-78
Published February 26, 2026
Last update February 26, 2026

CVSS base score

7.7/10
Attack vector Network
Attack complexity High
Privileges required Low
User interaction Required
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N

What the vulnerability does

01Description

WPGraphQL provides a GraphQL API for WordPress sites. Prior to version 2.9.1, the `wp-graphql/wp-graphql` repository contains a GitHub Actions workflow (`release.yml`) vulnerable to OS command injection through direct use of `${{ github.event.pull_request.body }}` inside a `run:` shell block. When a pull request from `develop` to `master` is merged, the PR body is injected verbatim into a shell command, allowing arbitrary command execution on the Actions runner. Version 2.9.1 contains a fix for the vulnerability.

Explanation of Vulnerability in Simple Terms

02Summary

WP GraphQL contains a code injection vulnerability in versions before 2.9.1. An attacker with low-level site access can inject and execute arbitrary code by crafting a malicious GraphQL query, but only if a victim visits a specially crafted link. The vulnerability affects data confidentiality and integrity across the site.

What an attacker can do

03Attacker Capabilities

Inject and execute arbitrary code on the site via a malicious GraphQL query.

Potential impact on your site

04Site Impact

An authenticated attacker can read sensitive data and modify site content if they can socially engineer a user to click a link.

Conditions required to exploit

05Prerequisites

Attacker needs low-level site access (e.g., subscriber account) and must trick a user into visiting a malicious link.

Key dates

06Disclosure timeline

February 26, 2026 CVE published
February 26, 2026 Record updated