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.
Published: 2026-08-03
Score: 4.8 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Microweber CMS 2.0.20 and earlier contain a stored cross‑site scripting flaw in the content tagging system. Admin‑authenticated attackers can inject arbitrary JavaScript by submitting malicious payloads through the tag_names parameter of the GET /api/save_content_admin endpoint, bypassing multiple sanitization controls including XSS middleware that ignores GET requests, a strip_unsafe() function that only removes double‑quoted onerror attributes, and a titlecase normalizer that leaves decimal‑entity encoded HTML unchanged. Stored scripts execute automatically for every visitor to public pages and within the admin editor, enabling session riding through same‑origin fetch requests that contain the CSRF token embedded in the page.

Affected Systems

Microweber CMS, version 2.0.20 and earlier. The issue is tied to the content tagging system and applies to configurations that allow administrative users to modify content tags.

Risk and Exploitability

The CVSS score of 4.8 indicates moderate severity, with an EPSS score of less than 1% and the vulnerability not listed in CISA’s KEV catalog. Based on the description, it is inferred that the attack requires authenticated admin access and can affect all site visitors through stored scripts. Exploitation chances depend on the presence of privileged administrative credentials and the lack of proper input filtering, making it a realistic threat in environments where administrators have broad permissions and content tagging is frequently used.

Generated by OpenCVE AI on August 4, 2026 at 21:05 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to Microweber 2.0.21 or later, or apply any vendor patch that removes the "tag_names" XSS flaw.
  • Restrict administrative access to trusted IP ranges or enable multi‑factor authentication to minimize the impact of any stored script that might be loaded.
  • Deploy a web application firewall or additional input validation that blocks JavaScript payloads on the "tag_names" parameter as a temporary mitigation until a patch is available.

Generated by OpenCVE AI on August 4, 2026 at 21:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 14 Aug 2026 17:15:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:microweber:microweber:*:*:*:*:*:*:*:*

Tue, 04 Aug 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 04 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
First Time appeared Microweber
Microweber microweber
Vendors & Products Microweber
Microweber microweber

Mon, 03 Aug 2026 22:15:00 +0000

Type Values Removed Values Added
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.
Title Microweber CMS 2.0.20 Stored XSS via tag_names Parameter
Weaknesses CWE-79
References
Metrics cvssV3_1

{'score': 4.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N'}

cvssV4_0

{'score': 4.8, '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'}


Subscriptions

Microweber Microweber
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-14T16:51:03.817Z

Reserved: 2026-07-29T21:07:39.203Z

Link: CVE-2026-67617

cve-icon Vulnrichment

Updated: 2026-08-04T14:09:48.643Z

cve-icon NVD

Status : Received

Published: 2026-08-03T22:16:50.963

Modified: 2026-08-04T15:16:40.860

Link: CVE-2026-67617

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-04T21:15:03Z

Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')