CVE-2026-4103: WSO2 API Control Plane · Cross-site Scripting
Affects WSO2 API Control PlaneSource CVE Database V5
Not known to be exploited · CVSS 6.4 Medium : upgrade to 4.6.0.19 or 4.5.0.55 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.6.0.19, 4.5.0.55, 4.6.0.18 +7
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 14 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WSO2WSO2 API Control Plane | Affected
| Fixed in
|
| WSO2WSO2 API Control Plane | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should verify with WSO2 for official fixes or updates addressing this vulnerability. If you cannot patch yet, restrict access to the affected portals to trusted users and consider additional input validation or content security policies to mitigate risk.
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.