{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102772 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102772 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102772 is a high-severity cross-site scripting vulnerability in jtsternberg CMB2, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-102772 and fix it if it is affected.\n\nWhat it is: CVE-2026-102772 is a high-severity cross-site scripting vulnerability in jtsternberg CMB2, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-102772 in the wild and no public exploit code.\n\nAffected product: jtsternberg CMB2. 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-102772/ (Markdown: https://insights.sbomify.com/CVE-2026-102772/index.md)","id":"CVE-2026-102772","markdown":"https://insights.sbomify.com/CVE-2026-102772/index.md","name":"CVE-2026-102772","record":{"aliases":["GHSA-3cr2-3237-fc84"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary scripts via the textarea_code field in the CMB2 WordPress plugin, leading to stored XSS.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The CMB2 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '\u003ctextarea_code field id\u003e (e.g. kl_code, kl_post_code)' parameter in all versions up to, and including, 2.13.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The front-end save path requires only a CMB2 box nonce, which is emitted to all visitors including unauthenticated guests via a simple GET request, making the attack trivially reachable without any credentials on sites that expose a public CMB2 form writing a textarea_code field.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"CMB2 \u003c= 2.13.1 - Unauthenticated Stored Cross-Site Scripting via 'textarea_code' Field","id":"CVE-2026-102772","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Cross-site scripting in SureDash – Community, Courses \u0026 Member Dashboard","id":"CVE-2026-102774"},"packages":[],"prev":{"headline":"Naichen ThinkCMF Email Template MailController.php templatePut special elements in template engine","id":"CVE-2026-102771"},"products":["CMB2"],"published":"2026-10-02","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-03","vendors":["jtsternberg"]},"summary":"Unauthenticated attackers can inject arbitrary scripts via the textarea_code field in the CMB2 WordPress plugin, leading to stored XSS.","url":"https://insights.sbomify.com/CVE-2026-102772/"}