Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2023-6911

MEDIUM

CVE-2023-6911 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in org.wso2.carbon.registry:carbon-registry. O3 Security confirms whether CVE-2023-6911 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

WSO2 Registry Stored Cross Site Scripting (XSS) vulnerability

Also known asGHSA-rfq3-wpjh-ppvg
Published
Dec 18, 2023
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  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

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-6911 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-6911. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects CVE-2023-6911 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.