Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-6911

Multiple WSO2 products have been identified as vulnerable due to improper output encoding, a Stored Cross Site Scripting (XSS) attack can…

Medium4.8EPSS 0.41%
Published
Updated
Reserved
Assigned by
WSO2

Description

Multiple WSO2 products have been identified as vulnerable due to improper output encoding, a Stored Cross Site Scripting (XSS) attack can be carried out by an attacker injecting a malicious payload into the Registry feature of the Management Console.

Scores

CVSS scores of CVE-2023-6911, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1Medium4.8CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
NVDNVD · Modified3.1Medium4.8CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
EPSS (exploitation in 30 days)
0.41% · top 65% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.8.

Weakness

Affected products

  • WSO2 · WSO2 API Manager

    • unknown < 2.2.0.0
    • affected 2.2.0.0 – < 2.2.0.1
    • affected 2.5.0.0 – < 2.5.0.1
    • affected 2.6.0.0 – < 2.6.0.1
    • affected 3.0.0.0 – < 3.0.0.1
    • affected 3.1.0.0 – < 3.1.0.1
    • affected 3.2.0.0 – < 3.2.0.1

  • WSO2 · WSO2 API Manager Analytics

    • unknown < 2.2.0.0
    • affected 2.2.0.0 – < 2.2.0.1
    • affected 2.5.0.0 – < 2.5.0.1

  • WSO2 · WSO2 API Microgateway

    • unknown < 2.2.0.0
    • affected 2.2.0.0 – < 2.2.0.1

  • WSO2 · WSO2 Data Analytics Server

    • unknown < 3.2.0.0
    • affected 3.2.0.0 – < 3.2.0.1

  • WSO2 · WSO2 Enterprise Integrator

    • unknown < 6.1.0.0
    • affected 6.1.0.0 – < 6.1.0.9
    • affected 6.1.1.0 – < 6.1.1.9
    • affected 6.2.0.0 – < 6.2.0.7
    • affected 6.3.0.0 – < 6.3.0.1
    • affected 6.4.0.0 – < 6.4.0.1
    • affected 6.5.0.0 – < 6.5.0.6
    • affected 6.6.0.0 – < 6.6.0.11

  • WSO2 · WSO2 IS as Key Manager

    • unknown < 5.5.0.0
    • affected 5.5.0.0 – < 5.5.0.1
    • affected 5.6.0.0 – < 5.6.0.1
    • affected 5.7.0.0 – < 5.7.0.1
    • affected 5.9.0.0 – < 5.9.0.1
    • affected 5.10.0.0 – < 5.10.0.1

  • WSO2 · WSO2 Identity Server

    • unknown < 5.4.0.0
    • affected 5.4.0.0 – < 5.4.0.4
    • affected 5.4.1.0 – < 5.4.1.3
    • affected 5.5.0.0 – < 5.5.0.1
    • affected 5.6.0.0 – < 5.6.0.1
    • affected 5.7.0.0 – < 5.7.0.1
    • affected 5.8.0.0 – < 5.8.0.5
    • affected 5.9.0.0 – < 5.9.0.1
    • affected 5.10.0.0 – < 5.10.0.1

  • WSO2 · WSO2 Identity Server Analytics

    • unknown < 5.4.0.0
    • affected 5.4.0.0 – < 5.4.0.2
    • affected 5.4.1.0 – < 5.4.1.2
    • affected 5.5.0.0 – < 5.5.0.1
    • affected 5.6.0.0 – < 5.6.0.1

  • WSO2 · WSO2 Message Broker

    • unknown < 3.2.0.0
    • affected 3.2.0.0 – < 3.2.0.3

Affected packages

From reviewed advisories of the GitHub Advisory Database.

What to do

Solution: For WSO2 Subscription holders, the recommended solution is to apply the provided patch/update to the affected versions of the products. If there are any instructions given with the patch/update, please make sure those are followed properly. Community users may apply the relevant fixes to the product based on the public fix(s) advertised in  https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2021/WSO2-2020-1... https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2021/WSO2-2020-1225/

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-6911 badge
[![CVE-2023-6911](https://trackcve.app/badge/CVE-2023-6911.svg)](https://trackcve.app/cve/CVE-2023-6911)

Record last updated .