{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-4093 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-4093 is a medium-severity cross-site scripting vulnerability in Drupal Term Reference Tree, published on 21 May 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-4093 and fix it if it is affected.\n\nWhat it is: CVE-2026-4093 is a medium-severity cross-site scripting vulnerability in Drupal Term Reference Tree, published on 21 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-4093 in the wild and no public exploit code.\n\nAffected product: Drupal Term Reference Tree. 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-4093/ (Markdown: https://insights.sbomify.com/CVE-2026-4093/index.md)","id":"CVE-2026-4093","markdown":"https://insights.sbomify.com/CVE-2026-4093/index.md","name":"CVE-2026-4093","record":{"aliases":["CLSA-2026-1789375926","GHSA-q6w2-7g3j-5vg3"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Drupal Term Reference Tree","requires_auth":"low_privilege","summary":"Stored XSS in Drupal Term Reference Tree allows attackers to inject scripts via term labels or token templates, potentially leading to session hijacking.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"drupal","cpe":[{"product":"taxonomy_term_reference_tree_widget","vendor":"taxonomy_term_reference_tree_widget_project"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"In the Drupal 7 Term Reference Tree module, two stored XSS vectors exist in the widget/formatter rendering pipeline.\n\nVector A (token display templates): When the Token module is enabled and token display templates are configured, attacker-controlled token output (e.g., term description) is rendered without proper sanitization. Any user who can edit the referenced taxonomy terms can inject HTML/JS that executes when the field is rendered.\n\nVector B (term label rendering): Taxonomy term labels are not properly sanitized before being rendered in the widget, allowing a user with permission to create or edit taxonomy terms to inject scripts into the term name that execute when a form containing the widget is viewed.\n\nExploit affects versions 7.x-1.x up to and including 7.x-1.11.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Stored XSS in Drupal 7 Term Reference Tree module (token display templates and term labels)","id":"CVE-2026-4093","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in FOX – Currency Switcher Professional for WooCommerce","id":"CVE-2026-4094"},"packages":[],"prev":{"headline":"Arbitrary File Write via Path Traversal in Google clasp leading to RCE","id":"CVE-2026-4092"},"products":["Term Reference Tree"],"published":"2026-05-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-05-22","vendors":["Drupal"]},"summary":"Stored XSS in Drupal Term Reference Tree allows attackers to inject scripts via term labels or token templates, potentially leading to session hijacking.","url":"https://insights.sbomify.com/CVE-2026-4093/"}