NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2023-6911 — carbon-registry

MEDIUMFix: wso2/carbon-registry@878fc7e

CVE-2023-6911 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in org.wso2.carbon.registry:carbon-registry. A fix is available for org.wso2.carbon.registry:carbon-registry — see the affected versions and patch details below.

WSO2 Registry Stored Cross Site Scripting (XSS) vulnerability

Also known asGHSA-rfq3-wpjh-ppvg
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk
0.00%0.30%0.60%0.91%0.3%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕org.wso2.carbon.registry:carbon-registry

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.wso2.carbon.registry:carbon-registryall versions4.7.37org.wso2.carbon.registry:carbon-registry:4.7.37

Affected Products

9 products · 35 configurations
Application
api managerwso2
6 versions
2.2.02.5.02.6.03.0.03.1.03.2.0
Application
api manager analyticswso2
2 versions
2.2.02.5.0
Application
api microgatewaywso2
1 version
2.2.0
Application
data analytics serverwso2
1 version
3.2.0
Application
enterprise integratorwso2
7 versions
6.1.06.1.16.2.06.3.06.4.06.5.06.6.0
Application
identity serverwso2
8 versions
5.4.05.4.15.5.05.6.05.7.05.8.05.9.05.10.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wso2.carbon.registry:carbon-registry, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.wso2.carbon.registry:carbon-registry to 4.7.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-6911 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2023-6911 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2023-6911: carbon-registry XSS — Fixed in 4.7.37