{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67617 exists.","fix":"No fix has been published for CVE-2026-67617 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-67617 is a medium-severity cross-site scripting vulnerability in microweber, published on 3 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-67617 and fix it if it is affected.\n\nWhat it is: CVE-2026-67617 is a medium-severity cross-site scripting vulnerability in microweber, published on 3 Aug 2026. An attacker needs administrator access to exploit it, 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-67617 exists.\n\nAffected product: microweber. 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-67617/ (Markdown: https://insights.sbomify.com/CVE-2026-67617/index.md)","id":"CVE-2026-67617","markdown":"https://insights.sbomify.com/CVE-2026-67617/index.md","name":"CVE-2026-67617","record":{"aliases":["GHSA-793c-7c93-m769"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Microweber CMS","requires_auth":"high_privilege","summary":"Admin-authenticated attackers can inject malicious JavaScript via the tag_names parameter, leading to script execution for visitors and potential session hijacking.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/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":"Microweber CMS through 2.0.20 contains a stored cross-site scripting vulnerability in the content tagging system that allows admin-authenticated attackers to inject arbitrary JavaScript by submitting malicious payloads via the tag_names parameter of the GET /api/save_content_admin endpoint, bypassing three independent sanitization controls including XSS middleware that ignores GET requests, a strip_unsafe() function that only matches double-quoted onerror attributes, and a titlecase normalizer that passes HTML decimal entity-encoded payloads through unchanged. Attackers can store malicious scripts that execute without user interaction for every visitor to the public blog page and within the admin post editor, enabling session riding through same-origin fetch requests using the CSRF token embedded in the page.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Microweber CMS 2.0.20 Stored XSS via tag_names Parameter","id":"CVE-2026-67617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"marimo \u003c 0.23.15 API Key Exfiltration via Malicious Notebook PEP-723 Metadata","id":"CVE-2026-67618"},"packages":[],"prev":{"headline":"Camaleon CMS 2.9.2 Missing Authorization via /admin/post_type drafts endpoint","id":"CVE-2026-67616"},"products":["microweber"],"published":"2026-08-03","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["microweber"]},"summary":"Admin-authenticated attackers can inject malicious JavaScript via the tag_names parameter, leading to script execution for visitors and potential session hijacking.","url":"https://insights.sbomify.com/CVE-2026-67617/"}