CVE-2026-67617: Microweber CMS 2.0.20 Stored XSS via tag_names Parameter
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 tagnames parameter of the GET /api/savecontentadmin endpoint, bypassing three independent sanitization controls including XSS middleware that ignores GET requests, a stripunsafe() 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-67617?
CVE-2026-67617 has a medium severity rating of 4.8.
How do I fix CVE-2026-67617?
To fix CVE-2026-67617, you should upgrade to a patched version of Microweber CMS that addresses the stored XSS vulnerability.
What is the impact of CVE-2026-67617?
CVE-2026-67617 allows admin-authenticated attackers to inject arbitrary JavaScript, which can lead to unauthorized actions or data exposure.
Which component of Microweber CMS is affected by CVE-2026-67617?
CVE-2026-67617 affects the content tagging system via the tag_names parameter in the /api/save_content_admin endpoint.
Who is at risk from CVE-2026-67617?
Admin-authenticated users of Microweber CMS are at risk from CVE-2026-67617.