Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessMisconfigure Event Publisher adapter with extraneous credential properties
-
DeliveryWSO2 logs unsanitized property values to wso2carbon log
-
ExploitAttacker gains local high-privilege access to log files
-
ExecutionParse logs to extract credentials
-
ImpactAuthenticate to target system or API as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A09:2025 - Security Logging & Alerting Failures
ASVS 5.0
V16 - Security Logging and Error Handling Log data sanitization
|
| Exploitation Conditions | Two conditions must simultaneously hold for exploitation to be possible: first, at least one Event Publisher output adapter must be configured with properties that are extraneous to the adapter's schema - this is a misconfiguration condition, not a default state; second, the attacker must have local, high-privileged read access to the wso2carbon log files on the host running the affected WSO2 product. The CVSS vector (AV:L/PR:H) confirms both constraints. Exploitation is limited by: (1) the requirement for a pre-existing misconfiguration of the Event Publisher adapter - correctly configured deployments do not trigger the logging behavior; (2) the need for local OS-level or administrative access to the log file path, ruling out remote unauthenticated attackers; and (3) the passive nature of the flaw - credentials are only logged when misconfigured adapters are invoked, not unconditionally. Deployments where Event Publisher is not used or is configured correctly are not affected. |
| Impact | The CVSS 3.1 base score of 4.4 Medium is calibrated by a local attack vector (AV:L) requiring high privileges (PR:H) - the attacker must already have OS-level or administrative read access to the wso2carbon log path. Despite the low score, the confidentiality impact is rated High (C:H) because the exposed data can include authentication credentials, enabling secondary compromise. EPSS data was not provided; given no KEV listing and no disclosed POC, opportunistic mass exploitation is not a current concern. The realistic threat profile is insider threat or post-compromise lateral movement: an attacker who has already achieved local system access or administrator-level credentials on the WSO2 host could harvest additional credentials from logs to pivot further. The 'Authentication Bypass' tag attached to this CVE is misleading - this is an information disclosure vulnerability (CWE-532) that could facilitate authentication bypass as a secondary outcome, not as a direct mechanism. Risk is moderate for organizations with shared WSO2 administrative access or insufficient log access controls; the specific trigger of an adapter misconfiguration limits exposure to environments where that misconfiguration exists. |
| Exploit ScenarioDerived | An insider threat - such as a system administrator or a DevOps engineer with shell access to the WSO2 host - navigates to the wso2carbon log directory and searches log entries for Event Publisher adapter property names known to carry credential values, such as passwords or API keys that were inadvertently passed as unsupported adapter properties by a misconfigured deployment. The administrator extracts these credentials from log entries and uses them to authenticate to downstream services or APIs as a higher-privileged user, bypassing normal authorization flows. No public exploit code is required; standard command-line log parsing tools are sufficient once log file access is obtained. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 06, 2026
Sensitive information disclosure in WSO2's Carbon Event Publisher Core affects nine WSO2 platform products, including API Manager, Identity Server, and Open Banking components. When an Event Publisher output adapter is misconfigured with extraneous or irrelevant properties, those property values - which may include user credentials or confidential data - are written to the wso2carbon log files without sanitization or masking (CWE-532). A local, high-privileged actor with read access to those log files can extract the inadvertently logged secrets and leverage them for unauthorized access. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
RemediationAI
Apply the vendor-released patch per WSO2 Security Advisory WSO2-2025-4897, available at https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4897/. The exact patched versions are not independently confirmed from the available input data - operators must consult the advisory directly to identify the minimum safe version for each affected product. As a compensating control, audit all Event Publisher output adapter configurations and remove any extraneous or unsupported properties that are not required by the adapter schema; eliminating the misconfiguration removes the trigger condition entirely. Additionally, enforce strict access controls on the wso2carbon log directory, limiting read access to only authorized system administrators via filesystem permissions (chmod 640 or equivalent) and centralised log management with role-based access. Note that restricting log access does not remediate the root cause but substantially reduces the exposure window by limiting who can read inadvertently logged secrets. Rotate any credentials that may have been written to logs prior to remediation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 9 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in the WSO2 Carbon Event Publisher Core component (cpe:2.3:a:wso2:wso2_carbon_event_publisher_core), a shared subsystem consumed across the WSO2 middleware platform. Event Publisher output adapters allow platform operators to route analytics or event data to external endpoints; each adapter accepts a typed property schema. When an operator configures properties outside that schema - so-called 'irrelevant properties' - the framework logs the full key-value pair to the wso2carbon log file without redacting or validating the values. CWE-532 (Insertion of Sensitive Information into Log File) describes exactly this root cause: application logging that inadvertently captures secrets because the logging layer does not differentiate between safe diagnostic data and sensitive runtime values. The affected product set spans API management (WSO2 API Manager, Traffic Manager, API Control Plane, Universal Gateway), identity and access management (WSO2 Identity Server, Identity Server as Key Manager), and regulated open banking deployments (WSO2 Open Banking IAM and AM).
Know when Wso2 Api Manager gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Local attack vector and high privileges required because exploitation demands filesystem read access to wso2carbon logs; confidentiality High as credentials may be exposed; no integrity or availability impact.
Primary rating from Vendor (WSO2).
CVSS VectorVendor: WSO2
Lifecycle Timeline
1DescriptionCVE.org
When an Event Publisher output adapter is configured with irrelevant properties, the affected products log these properties. This logging occurs without sufficient validation or sanitization of the property values.
A malicious actor with access to the 'wso2carbon' log files could retrieve sensitive information, such as user credentials or other confidential data, that was inadvertently logged due to misconfiguration, potentially leading to unauthorized access.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Wso2 Api Manager
View allAuthentication bypass in WSO2 API Manager and related components (Universal Gateway, Traffic Manager, API Control Plane,
Server-side request forgery in WSO2 API Manager lets unauthenticated remote attackers coerce the gateway into making ser
Privilege escalation in WSO2 API Manager and related Carbon-based products allows a low-privileged user, using a validly
Authentication bypass in WSO2 Identity Server and multiple WSO2 platform products (API Manager, Open Banking AM/IAM/KM,
Missing role-based authorization on WSO2 API Manager's Gateway REST API lets any authenticated user invoke privileged Ga
Persistent denial of service in multiple WSO2 products - including WSO2 API Manager, WSO2 Universal Gateway, WSO2 Traffi
OS command injection (CWE-78) in WSO2's shared Carbon Console administrative interface allows an authenticated administr
Server-side request forgery in WSO2 API Manager and related WSO2 products lets a remote attacker direct the server to ar
Predictable HMAC shared secrets generated by the API Publisher component of WSO2 API Manager allow a sophisticated attac
HTTP response header injection in WSO2 API Manager and its companion WSO2 gateway components (Universal Gateway, Traffic
The XML parsers within multiple WSO2 products accept user-supplied XML data without properly configuring to prevent the
WSO2 Carbon OAuth, as shipped in WSO2 Identity Server, API Manager, and related WSO2 products, can leave session-bound t
EUVD-2026-53820
GHSA-q9jj-jm6w-fpgf
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB