Cross-Site Scripting via HTML Sanitization in WSO2 Publisher and Developer Portals Allows Malicious Script Execution (CVE-2026-4103) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-4103

Cross-Site Scripting via HTML Sanitization in WSO2 Publisher and Developer Portals Allows Malicious Script Execution

Answer in brief

CVE-2026-4103 records a Unknown severity vulnerability in Cross-Site Scripting via HTML Sanitization in WSO2 Publisher and Developer Portals Allows Malicious Script Execution. The current sources do not mark it as known exploited. The current feed maps WSO2/WSO2 API Control Plane (generic), WSO2/WSO2 API Manager (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 14, 2026Updated Sep 14, 2026Source checked Sep 14, 2026First seen by HOL Sep 14, 2026Material review Sep 14, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps WSO2/WSO2 API Control Plane (generic), WSO2/WSO2 API Manager (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
WSO2/WSO2 API Control Planegeneric	>=4.5.0 <4.5.0.55 \|\| >=4.6.0 <4.6.0.19	4.5.0.55, 4.6.0.19
WSO2/WSO2 API Managergeneric	>=3.2.0 <3.2.0.470 \|\| >=3.2.1 <3.2.1.89 \|\| >=4.1.0 <4.1.0.254 \|\| >=4.2.0 <4.2.0.194 \|\| >=4.3.0 <4.3.0.105 \|\| >=4.4.0 <4.4.0.69 \|\| >=4.5.0 <4.5.0.54 \|\| >=4.6.0 <4.6.0.18	3.2.0.470, 3.2.1.89, 4.1.0.254, 4.2.0.194, 4.3.0.105, 4.4.0.69, 4.5.0.54, 4.6.0.18

Recommended response

Check inventory. Check lockfiles and deployed manifests for WSO2/WSO2 API Control Plane, WSO2/WSO2 API Manager.
Review the reported fix. Update WSO2/WSO2 API Control Plane to 4.5.0.55; WSO2/WSO2 API Manager to 3.2.0.470 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 14, 2026

Sources and claim methodology

Source referencesecurity.docs.wso2.com

Upstream source description

Insufficient HTML sanitization in the Publisher Portal and Developer Portal allows untrusted user input to be rendered without proper encoding or neutralization. This enables the injection and execution of malicious JavaScript when affected API documents are viewed. Successful exploitation may result in the execution of malicious scripts within the user's browser context when viewing API documentation. Users with permissions to access the API documentation through these portals may be impacted, potentially allowing attackers to perform actions on behalf of the user, depending on their session privileges.

Quoted source text, attributed separately from HOL analysis.