{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27938 exists.","fix":"No fix has been published for CVE-2026-27938 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27938 is a high-severity command injection vulnerability in wp-graphql, published on 26 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-27938 and fix it if it is affected.\n\nWhat it is: CVE-2026-27938 is a high-severity command injection vulnerability in wp-graphql, published on 26 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27938 exists.\n\nAffected product: wp-graphql. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-27938/ (Markdown: https://insights.sbomify.com/CVE-2026-27938/index.md)","id":"CVE-2026-27938","markdown":"https://insights.sbomify.com/CVE-2026-27938/index.md","name":"CVE-2026-27938","record":{"aliases":["GHSA-4q9f-mjxf-rx7x"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions workflow","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary commands on CI runners by injecting shell code into pull request bodies during release workflows.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-04","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-04T19:08:34Z","kind":"github_poc","ref":"https://github.com/pvharmo2/gha-lab-a7f6217d26","stars":0,"title":"Security-research reproduction of CVE-2026-27938 / GHSA-4q9f-mjxf-rx7x (GitHub Actions expression injection in release workflows) — snapshot of wp-graphql/wp-graphql at b216fe22f3a119f256511ec7353f536fee6886ac"}],"tier":"weaponised"},"has_fix":false,"headline":"WPGraphQL Repo Vulnerable to Command Injection via Unsanitized GitHub Actions Expression in Release Workflow","id":"CVE-2026-27938","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Statamic allows Authenticated Control Panel users to escalate privileges via elevated session bypass","id":"CVE-2026-27939"},"packages":[],"prev":{"headline":"October: Reflected XSS via DataTable Form Widget","id":"CVE-2026-27937"},"products":["wp-graphql"],"published":"2026-02-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["wp-graphql"]},"summary":"Attackers can execute arbitrary commands on CI runners by injecting shell code into pull request bodies during release workflows.","url":"https://insights.sbomify.com/CVE-2026-27938/"}