{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119702 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-119702 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119702 is a medium-severity vulnerability in WPGraphQL, published on 30 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-119702 and fix it if it is affected.\n\nWhat it is: CVE-2026-119702 is a medium-severity vulnerability in WPGraphQL, published on 30 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-119702 in the wild and no public exploit code.\n\nAffected product: WPGraphQL. 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-119702/ (Markdown: https://insights.sbomify.com/CVE-2026-119702/index.md)","id":"CVE-2026-119702","markdown":"https://insights.sbomify.com/CVE-2026-119702/index.md","name":"CVE-2026-119702","record":{"aliases":["GHSA-4vgv-vvxr-9fh9","GHSA-wj7h-xjr7-93c6"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"WPGraphQL before 2.24.1 contains a missing authorization vulnerability in the createComment mutation that allows unauthenticated attackers to comment on non-public posts by bypassing post status checks. Attackers can attach comments to draft, private, trashed, or password-protected posts to leak hidden titles via moderator notifications, enumerate post IDs, and backdate comments or mark them as pingbacks.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"WPGraphQL before 2.24.1 Missing Authorization via createComment Mutation","id":"CVE-2026-119702","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"xiaozhi-esp32-server through 0.9.8 Authentication Bypass via Spoofed Device-ID Header","id":"CVE-2026-119703"},"nickname":null,"packages":[],"prev":{"headline":"WPGraphQL before 2.24.1 Email Flooding via Aliased sendPasswordResetEmail Mutations","id":"CVE-2026-119701"},"products":["WPGraphQL"],"published":"2026-10-30","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)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-30","vendors":["WPGraphQL"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119702/"}