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.