Stored XSS via tag_names sanitization bypasses
Published Aug 3, 2026 · Updated Aug 3, 2026
Stored XSS in Microweber CMS through 2.0.20 allows remote authenticated users to execute JavaScript through crafted content tag names. The save_content_admin endpoint accepts tag_names by GET, bypassing XSS middleware, while strip_unsafe misses unquoted handlers and title normalization preserves decimal entities. Administrator access is required to store the tag; opening the public blog or admin editor then executes it without further interaction, enabling same-origin session riding.
Summary
What happened
Stored XSS in Microweber CMS through 2.0.20 allows remote authenticated users to execute JavaScript through crafted content tag names. The save_content_admin endpoint accepts tag_names by GET, bypassing XSS middleware, while strip_unsafe misses unquoted handlers and title normalization preserves decimal entities. Administrator access is required to store the tag; opening the public blog or admin editor then executes it without further interaction, enabling same-origin session riding.
The record
- CVE
- CVE-2026-67617
- Published
- Aug 3, 2026
- Updated
- Aug 3, 2026
- Vendor
- Microweber
- Product
- Microweber
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Aug 3, 2026CVE publishedPublication date reported by the CVE source.
- Aug 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.0.20
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Stored XSS via Content Tag Names proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo