WSO2 products vulnerable to XML External Entity attack

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

EPSS

• CVE-2023-6836: 0.48% estimated exploitation activity in the next 30 days; percentile 41.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Multiple WSO2 products have been identified as vulnerable due to an XML External Entity (XXE) attack abuses a widely available but rarely used feature of XML parsers to access sensitive information.

Published by the source

15 Dec 2023, 12:30 UTC

Last modified by the source

19 Dec 2023, 20:52 UTC

Source last checked

26 Oct 2026, 16:21 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cr8h-fr86-8vfv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-6836

Advisory: WSO2 products vulnerable to XML External Entity attack
IDs: CVE-2023-6836, GHSA-cr8h-fr86-8vfv
Record: https://patchnext.com/advisories/cve-2023-6836 (revision 1, source checked 26 Oct 2026, 16:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.wso2.carbon.governance:org.wso2.carbon.governance.common 4.8.13; org.wso2.am:wso2am 4.0.0-beta; org.wso2.carbon.commons:org.wso2.carbon.ntask.core 4.7.24; org.wso2.carbon.analytics-common:org.wso2.carbon.event.input.adapter.core 5.2.23; org.wso2.carbon.registry:org.wso2.carbon.registry.extensions 4.7.31; org.wso2.carbon.event-processing:org.wso2.carbon.event.processor.core 2.2.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.wso2.carbon.governance:org.wso2.carbon.governance.common: affected < 4.8.13; fixed in 4.8.13
- Maven org.wso2.am:wso2am: affected < 4.0.0-beta; fixed in 4.0.0-beta
- Maven org.wso2.carbon.commons:org.wso2.carbon.ntask.core: affected < 4.7.24; fixed in 4.7.24
- Maven org.wso2.carbon.analytics-common:org.wso2.carbon.event.input.adapter.core: affected < 5.2.23; fixed in 5.2.23
- Maven org.wso2.carbon.registry:org.wso2.carbon.registry.extensions: affected < 4.7.31; fixed in 4.7.31
- Maven org.wso2.carbon.event-processing:org.wso2.carbon.event.processor.core: affected < 2.2.12; fixed in 2.2.12

## Suggested inspection (read-only)
- Maven org.wso2.carbon.governance:org.wso2.carbon.governance.common: check the installed version with your package manager.
- Maven org.wso2.am:wso2am: check the installed version with your package manager.
- Maven org.wso2.carbon.commons:org.wso2.carbon.ntask.core: check the installed version with your package manager.
- Maven org.wso2.carbon.analytics-common:org.wso2.carbon.event.input.adapter.core: check the installed version with your package manager.
- Maven org.wso2.carbon.registry:org.wso2.carbon.registry.extensions: check the installed version with your package manager.
- Maven org.wso2.carbon.event-processing:org.wso2.carbon.event.processor.core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.wso2.carbon.governance:org.wso2.carbon.governance.common, org.wso2.am:wso2am, org.wso2.carbon.commons:org.wso2.carbon.ntask.core, org.wso2.carbon.analytics-common:org.wso2.carbon.event.input.adapter.core, org.wso2.carbon.registry:org.wso2.carbon.registry.extensions, org.wso2.carbon.event-processing:org.wso2.carbon.event.processor.core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cr8h-fr86-8vfv (GitHub-reviewed advisory GHSA-cr8h-fr86-8vfv lists affected ranges: Maven org.wso2.carbon.commons:org.wso2.carbon.ntask.core >=0 =0 =0 =0 =0 <5.2.23; Maven…)

Commands are suggestions: review each one before running it.