CVE-2024-6541 — Information Disclosure and Integrity Violation via Improper Message Context Handling in Multiple WSO2 Products
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+4
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (WSO2 Api Manager, WSO2 Enterprise Integrator, WSO2 Micro Integrator…).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| WSO2 | Api Manager | ≥ 3.2.1 and < 3.2.1.21≥ 4.0.0 and < 4.0.0.311≥ 4.1.0 and < 4.1.0.167≥ 4.2.0 and < 4.2.0.110≥ 4.3.0 and < 4.3.0.24≥ 3.2.0 and < 3.2.0.394 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Enterprise Integrator | ≥ 6.6.0 and < 6.6.0.205 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Micro Integrator | ≥ 4.3.0 and < 4.3.0.7≥ 4.1.0 and < 4.1.0.103≥ 1.2.0 and < 1.2.0.163 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | WSO2-Synapse |
≥ 2.1.7.wso2v182 and < 2.1.7.wso2v182_93≥ 2.1.7.wso2v143 and < 2.1.7.wso2v143_119≥ 2.1.7.wso2v183 and < 2.1.7.wso2v183_62≥ 2.1.7.wso2v319 and < 2.1.7.wso2v319_7≥ 2.1.7.wso2v227 and < 2.1.7.wso2v227_88≥ 2.1.7.wso2v271 and < 2.1.7.wso2v271_60≥ 4.0.0.wso2v119 and < 4.0.0.wso2v119_3≥ 4.0.0.wso2v105 and < 4.0.0.wso2v105_3 and 1 more≥ 4.0.0.wso2v20 and < 4.0.0.wso2v20_63 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.8 | CVSS 3.1 | Medium | 1.6 | 5.2 | ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database |
| 6.8 | CVSS 3.1 | Medium | — | — | WSO2 via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N (score shown at the top: ed10eef1-636d-4fbe-9993-6890dfa878f8) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · wso2/wso2 micro integrator, wso2/wso2 enterprise integrator, wso2/wso2 api manager, wso2/wso2-synapse
- SSVC assessment updated
- Record published
- CVSS changed · 6.8
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2025-5802 Username Enumeration via Self Registration Flow in Multiple WSO2 Products Allows User Account Discovery Sep 15, 2026
- Medium CVE-2026-4103 Cross-Site Scripting via HTML Sanitization in WSO2 Publisher and Developer Portals Allows Malicious Script Execution Sep 14, 2026
- Medium CVE-2026-3096 Reverse Tabnabbing via New Tab Navigation in Multiple WSO2 Products Allows Phishing and Credential Theft Sep 10, 2026
- High CVE-2025-12737 Arbitrary Code Execution via Administrative Operations in Multiple WSO2 Products Allows Remote Code Execution Sep 3, 2026
- High CVE-2026-3416 Predictable Pseudorandom Number Generation via Webhook HMAC Secret Generation in Multiple WSO2 Products Allows Forged Event Payloads Sep 3, 2026
- Critical CVE-2026-3418 Arbitrary File Upload via System REST API in Multiple WSO2 Products Allows Remote Code Execution Aug 6, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-6541 is "Information Disclosure and Integrity Violation via Improper Message Context Handling in Multiple WSO2 Products", rated Medium. It affects Api Manager (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.8 describes technical severity. EPSS 0.34% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.