Security Advisory WSO2-2025-4829/CVE-2026-0637¶
Published: 2026-05-03
Version: 1.0.0
Severity: Medium
CVSS Score: 5.4 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N)
CVE IDs: CVE-2026-0637
AFFECTED PRODUCTS¶
- WSO2 API Control Plane: 4.6.0, 4.5.0
- WSO2 API Manager: 4.6.0, 4.5.0, 4.4.0, 4.3.0, 4.2.0, 4.1.0, 3.2.1, 3.2.0
OVERVIEW¶
Potential header injection.
DESCRIPTION¶
When a proxy server is configured with “customUrl.enabled”, a malicious actor can manipulate forwarded HTTP headers to influence URL construction, leading to an open redirect vulnerability. Additionally, unsanitized header values may be written to application logs, potentially leading to log forgery.
IMPACT¶
An attacker can force redirection to malicious domains and inject forged entries into application logs, potentially enabling phishing attacks and impacting the reliability of security logs.
SOLUTION¶
Community Users (Open Source)¶
Apply the relevant fixes to your product using the public fix(es) provided below.
If applying the fix or update is not feasible, migrate to the latest unaffected version of the respective WSO2 product(s).
Support Subscription Holders¶
Update your product to the specified update level, or to a higher update level, to mitigate the identified vulnerability.
Info
WSO2 Support Subscription Holders may use WSO2 Updates in order to apply the fix.
| Product Name | Product Version | Update Level |
|---|---|---|
| WSO2 API Control Plane | 4.6.0 | 13 |
| WSO2 API Control Plane | 4.5.0 | 45 |
| WSO2 API Manager | 4.6.0 | 12 |
| WSO2 API Manager | 4.5.0 | 44 |
| WSO2 API Manager | 4.4.0 | 63 |
| WSO2 API Manager | 4.3.0 | 99 |
| WSO2 API Manager | 4.2.0 | 189 |
| WSO2 API Manager | 4.1.0 | 249 |
| WSO2 API Manager | 3.2.1 | 83 |
| WSO2 API Manager | 3.2.0 | 464 |
After applying the provided update or public PR to the affected product versions, it is necessary to follow the below given instruction.
For WSO2 API Manager versions 4.2.0, 4.3.0, 4.4.0, 4.5.0, and 4.6.0:
Edit the settings.json file at the relevant portal paths to safeguard your deployment:
/repository/deployment/server/webapps/publisher/site/public/conf/settings.json /repository/deployment/server/webapps/devportal/site/public/theme/settings.json /repository/deployment/server/webapps/admin/site/public/conf/settings.json
Add or update the following configuration to define the allowed hosts:
app.customUrl.allowedHosts = ["domain1.com", "domain2.com"]
Note: Replace "domain1.com" and "domain2.com" with the trusted domain names used in your specific deployment.
For WSO2 API Manager versions 4.1.0 and below (including 4.0.0 and earlier)
Update the configuration in the settings.js file at the relevant paths:
/repository/deployment/server/jaggeryapps/publisher/site/public/conf/settings.js /repository/deployment/server/jaggeryapps/devportal/site/public/theme/settings.js /repository/deployment/server/jaggeryapps/admin/site/public/conf/settings.js
Configure the allowed hosts as follows:
app.customUrl.allowedHosts = ["domain1.com", "domain2.com"]