CVE-2023-6836

HIGHNVD 7.54.6
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.6 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
4.6(low)
EPSS
38.2%
KEV
Not listed

Published

December 15, 2023

Last Modified

June 17, 2026

References (2)

Affected Packages

(6 across 1 ecosystem)
Maven(6)
PackageVulnerable rangeFixed inDependents
org.wso2.am:wso2am—4.0.0-beta—
org.wso2.carbon.analytics-common:org.wso2.carbon.event.input.adapter.core1.0.0 ... 5.2.19 (86 versions)5.2.23—
org.wso2.carbon.commons:org.wso2.carbon.ntask.core4.3.0 ... 4.7.22 (102 versions)4.7.24—
org.wso2.carbon.event-processing:org.wso2.carbon.event.processor.core2.0.1 ... 2.2.6 (50 versions)2.2.12—
org.wso2.carbon.governance:org.wso2.carbon.governance.common4.5.0 ... 4.8.9 (51 versions)4.8.13—
org.wso2.carbon.registry:org.wso2.carbon.registry.extensions4.6.11 ... 4.7.28 (41 versions)4.7.31—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:45 UTCEPSS rescore
  2. 2026-07-12 05:45 UTCEPSS rescore
  3. 2026-07-11 08:26 UTCEPSS rescore
  4. 2026-07-09 19:08 UTCEPSS rescore
  5. 2026-07-08 15:13 UTCEPSS rescore
  6. 2026-07-07 13:45 UTCEPSS rescore
  7. 2026-07-07 13:44 UTCEPSS rescore
  8. 2026-07-06 02:22 UTCEPSS rescore
  9. 2026-07-06 02:22 UTCEPSS rescore
  10. 2026-07-05 02:29 UTCEPSS rescore
  11. 2026-07-04 06:29 UTCEPSS rescore
  12. 2026-07-01 15:05 UTCEPSS rescore
  13. 2026-06-30 23:21 UTCEPSS rescore
  14. 2026-06-30 23:21 UTCEPSS rescore
  15. 2026-06-29 14:05 UTCEPSS rescore
  16. 2026-06-28 14:06 UTCEPSS rescore
  17. 2026-06-28 14:06 UTCEPSS rescore
  18. 2026-06-28 04:55 UTCEPSS rescore
  19. 2026-06-27 03:07 UTCEPSS rescore
  20. 2026-06-25 13:48 UTCEPSS rescore
  21. 2026-06-25 13:48 UTCEPSS rescore
  22. 2026-06-24 19:31 UTCOSV refresh
  23. 2026-06-24 14:04 UTCEPSS rescore
  24. 2026-06-24 14:04 UTCEPSS rescore
  25. 2026-06-24 06:34 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
Show 52 more
  1. 2026-06-23 21:31 UTCEPSS rescore
  2. 2026-06-23 21:31 UTCEPSS rescore
  3. 2026-06-22 14:24 UTCEPSS rescore
  4. 2026-06-22 14:24 UTCEPSS rescore
  5. 2026-06-21 14:55 UTCEPSS rescore
  6. 2026-06-21 14:55 UTCEPSS rescore
  7. 2026-06-21 01:58 UTCEPSS rescore
  8. 2026-06-21 01:58 UTCEPSS rescore
  9. 2026-06-19 19:24 UTCEPSS rescore
  10. 2026-06-19 19:24 UTCEPSS rescore
  11. 2026-06-18 17:51 UTCEPSS rescore
  12. 2026-06-17 17:51 UTCEPSS rescore
  13. 2026-06-16 17:51 UTCEPSS rescore
  14. 2026-06-16 17:51 UTCEPSS rescore
  15. 2026-06-15 17:47 UTCEPSS rescore
  16. 2026-06-14 23:16 UTCEPSS rescore
  17. 2026-06-13 22:59 UTCEPSS rescore
  18. 2026-06-13 22:59 UTCEPSS rescore
  19. 2026-06-12 23:11 UTCEPSS rescore
  20. 2026-06-11 13:59 UTCEPSS rescore
  21. 2026-06-10 22:17 UTCEPSS rescore
  22. 2026-06-10 13:21 UTCEPSS rescore
  23. 2026-06-08 14:16 UTCEPSS rescore
  24. 2026-06-08 14:16 UTCEPSS rescore
  25. 2026-06-07 20:16 UTCOSV refresh
  26. 2026-06-07 15:24 UTCEPSS rescore
  27. 2026-06-07 15:24 UTCEPSS rescore
  28. 2026-06-06 13:46 UTCEPSS rescore
  29. 2026-06-06 13:46 UTCEPSS rescore
  30. 2026-06-05 22:46 UTCEPSS rescore
  31. 2026-06-05 22:46 UTCEPSS rescore
  32. 2026-06-05 06:09 UTCEPSS rescore
  33. 2026-06-05 06:09 UTCEPSS rescore
  34. 2026-06-04 13:11 UTCEPSS rescore
  35. 2026-06-04 13:11 UTCEPSS rescore
  36. 2026-06-02 20:12 UTCEPSS rescore
  37. 2026-06-02 20:12 UTCEPSS rescore
  38. 2026-06-01 13:51 UTCEPSS rescore
  39. 2026-05-31 22:30 UTCEPSS rescore
  40. 2026-05-31 22:30 UTCEPSS rescore
  41. 2026-05-31 00:15 UTCEPSS rescore
  42. 2026-05-31 00:15 UTCEPSS rescore
  43. 2026-05-29 13:43 UTCEPSS rescore
  44. 2026-05-28 13:44 UTCEPSS rescore
  45. 2026-05-28 13:44 UTCEPSS rescore
  46. 2026-05-27 13:40 UTCEPSS rescore
  47. 2026-05-27 13:39 UTCEPSS rescore
  48. 2026-05-26 13:43 UTCEPSS rescore
  49. 2026-05-26 13:43 UTCEPSS rescore
  50. 2026-05-26 07:18 UTCEPSS rescore
  51. 2026-05-26 07:18 UTCEPSS rescore
  52. 2026-05-23 10:07 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-6836?
CVE-2023-6836 is a high vulnerability published on December 15, 2023. 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.
When was CVE-2023-6836 disclosed?
CVE-2023-6836 was first published in the National Vulnerability Database on December 15, 2023, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-6836 actively exploited?
CVE-2023-6836 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 38.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-6836?
CVE-2023-6836 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 4.6. The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2023-6836?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-6836, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-6836

Explore →

Is Your Infrastructure Affected by CVE-2023-6836?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs