Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2024-6541

Information Disclosure and Integrity Violation via Improper Message Context Handling in Multiple WSO2 Products

Medium6.8EPSS 0.34%
Published
Updated
Reserved
Assigned by
WSO2

Description

The Class Mediator fails to correctly validate or sanitize `messageContext` properties when they are used to populate dynamic values. This allows authenticated users to potentially access or modify data across different system invocations that should be isolated. This weakness can lead to the disclosure of sensitive information belonging to other users or the unintended modification of system data by authenticated users. The exact impact depends on how `messageContext` properties are utilized within the affected WSO2 products.

Scores

CVSS scores of CVE-2024-6541, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1Medium6.8CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
NVDNVD · Deferred3.1Medium6.8CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS (exploitation in 30 days)
0.34% · top 72% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.8.

Weakness

Affected products

  • WSO2 · WSO2 Micro Integrator

    • unknown < 1.2.0
    • affected 1.2.0 – < 1.2.0.163
    • affected 4.1.0 – < 4.1.0.103
    • affected 4.3.0 – < 4.3.0.7
  • WSO2 · WSO2 Enterprise Integrator

    • unknown < 6.6.0
    • affected 6.6.0 – < 6.6.0.205
  • WSO2 · WSO2 API Manager

    • unknown < 3.2.0
    • affected 3.2.0 – < 3.2.0.394
    • affected 3.2.1 – < 3.2.1.21
    • affected 4.0.0 – < 4.0.0.311
    • affected 4.1.0 – < 4.1.0.167
    • affected 4.2.0 – < 4.2.0.110
    • affected 4.3.0 – < 4.3.0.24
  • WSO2 · WSO2-Synapse

    • affected 2.1.7.wso2v182 – < 2.1.7.wso2v182_93
    • affected 2.1.7.wso2v143 – < 2.1.7.wso2v143_119
    • affected 2.1.7.wso2v183 – < 2.1.7.wso2v183_62
    • affected 2.1.7.wso2v319 – < 2.1.7.wso2v319_7
    • affected 2.1.7.wso2v227 – < 2.1.7.wso2v227_88
    • affected 2.1.7.wso2v271 – < 2.1.7.wso2v271_60
    • affected 4.0.0.wso2v119 – < 4.0.0.wso2v119_3
    • affected 4.0.0.wso2v105 – < 4.0.0.wso2v105_3
    • affected 4.0.0.wso2v20 – < 4.0.0.wso2v20_63
    • unaffected v4.0.0-wso2v121 – ≤ v4.0.0-wso2v*

What to do

Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3520/#solution https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3520/#solution

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-6541 badge
[![CVE-2024-6541](https://trackcve.app/badge/CVE-2024-6541.svg)](https://trackcve.app/cve/CVE-2024-6541)

Record last updated .