CVE-2026-0637

Header Injection via Custom URL Configuration in Multiple WSO2 Products Allows Open Redirect and Log Forgery

Published Aug 6, 2026 CVSS 3.1 · 5.4 Medium EPSS < 1% KEV · Not listed
Description
When a proxy server is configured with `customUrl.enabled`, the component accepts user-supplied input within forwarded HTTP headers without enforcing expected validation constraints. A malicious actor can manipulate these headers to influence the URL construction process, leading to an open redirect vulnerability. Additionally, unsanitized header values are written to application logs.

An attacker can exploit this to force redirection to arbitrary malicious domains, potentially enabling phishing attacks. Furthermore, they can inject forged entries into application logs, impacting the reliability of security logs and potentially hindering incident investigation.

Analysis

AI-generated

Technical impact

A flaw in WSO2 products is triggered when a proxy server is configured with customUrl.enabled. The component accepts user‑supplied values in forwarded HTTP headers without validating them. A malicious actor can manipulate these headers to influence the URL construction process, creating an open redirect that can lead users to arbitrary malicious sites. In addition, the unsanitized header values are written to application logs, enabling forged entries that can corrupt log integrity and hamper incident investigations.

Affected Systems

The vulnerability affects the WSO2 API Control Plane and the WSO2 API Manager. No specific software version is provided, meaning all current releases of these products are potentially impacted.

Risk and Exploitability

The CVSS score of 5.4 denotes moderate severity. The EPSS score is less than 1 %, indicating a very low exploitation probability at the time of release. The vulnerability is not listed in the CISA KEV catalog. An attacker can exploit the flaw remotely by sending a crafted HTTP request to a proxy server with customUrl.enabled enabled and forging header values that are forwarded into the URL construction logic. This allows the attacker to redirect users to any domain, facilitating phishing, or to inject forged entries into application logs to obscure real activity. The attack requires remote access to the proxy server configuration, but legitimate users can be affected by the redirect without needing privileged local access. Overall risk remains moderate, with primary concerns of user redirection and compromised logging integrity.

Remediation

Vendor Solution

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


OpenCVE Recommended Actions

  • Follow the instructions provided in the official advisory at https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4829/#solution.
  • If a patch cannot be applied immediately, disable the customUrl.enabled feature or enforce strict validation of forwarded HTTP headers to prevent header injection.
  • Restrict file system permissions for application log files so that only authorized users can read or modify them, mitigating log forging.

Generated by OpenCVE AI on November 4, 2026 at 15:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description 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. When a proxy server is configured with `customUrl.enabled`, the component accepts user-supplied input within forwarded HTTP headers without enforcing expected validation constraints. A malicious actor can manipulate these headers to influence the URL construction process, leading to an open redirect vulnerability. Additionally, unsanitized header values are written to application logs. An attacker can exploit this to force redirection to arbitrary malicious domains, potentially enabling phishing attacks. Furthermore, they can inject forged entries into application logs, impacting the reliability of security logs and potentially hindering incident investigation.
Title Sensitive Information Disclosure via Event Publisher Logging in Multiple WSO2 Products Header Injection via Custom URL Configuration in Multiple WSO2 Products Allows Open Redirect and Log Forgery
Weaknesses CWE-20
CWE-74
Metrics cvssV3_1

{'score': 4.4, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N'}

cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N'}

Type Values Removed Values Added
First Time appeared Wso2 api Control Plane
Wso2 api Manager
Wso2 identity Server
Wso2 identity Server As Key Manager
Wso2 open Banking Am
Wso2 open Banking Iam
Wso2 traffic Manager
Wso2 universal Gateway
CPEs cpe:2.3:a:wso2:api_control_plane:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:api_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:identity_server:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:identity_server_as_key_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:open_banking_am:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:open_banking_iam:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:traffic_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:universal_gateway:*:*:*:*:*:*:*:*
Vendors & Products Wso2 api Control Plane
Wso2 api Manager
Wso2 identity Server
Wso2 identity Server As Key Manager
Wso2 open Banking Am
Wso2 open Banking Iam
Wso2 traffic Manager
Wso2 universal Gateway
Type Values Removed Values Added
First Time appeared Wso2
Wso2 wso2 Api Control Plane
Wso2 wso2 Api Manager
Wso2 wso2 Carbon Event Publisher Core
Wso2 wso2 Identity Server
Wso2 wso2 Identity Server As Key Manager
Wso2 wso2 Open Banking Am
Wso2 wso2 Open Banking Iam
Wso2 wso2 Traffic Manager
Wso2 wso2 Universal Gateway
Vendors & Products Wso2
Wso2 wso2 Api Control Plane
Wso2 wso2 Api Manager
Wso2 wso2 Carbon Event Publisher Core
Wso2 wso2 Identity Server
Wso2 wso2 Identity Server As Key Manager
Wso2 wso2 Open Banking Am
Wso2 wso2 Open Banking Iam
Wso2 wso2 Traffic Manager
Wso2 wso2 Universal Gateway
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Sensitive Information Disclosure via Event Publisher Logging in Multiple WSO2 Products
Weaknesses CWE-532
References
Metrics cvssV3_1

{'score': 4.4, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N'}