EUVD-2025-209758
GHSA-j72f-vgmh-c8hr
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionCVE.org
In Webhook API invocations, the component accepts user-supplied input for HTTP request headers without sufficient validation or sanitization, allowing these headers to be injected into HTTP responses.
By exploiting this vulnerability, a malicious actor can inject or overwrite arbitrary HTTP response headers. This can lead to various adverse effects, including the manipulation of browser caching, alteration of security-related headers, and the injection of sensitive information such as cookie values, potentially enabling session hijacking or other malicious activities.
AnalysisAI
HTTP response header injection in WSO2 Webhook API invocations allows unauthenticated remote attackers to inject or overwrite arbitrary HTTP response headers via unsanitized user-supplied input. Successful exploitation enables cache manipulation, security header alteration, cookie injection, and potential session hijacking. CVSS 5.3 (network-accessible, low complexity, no authentication required); no public exploit code or active exploitation confirmed at time of analysis.
Technical ContextAI
The vulnerability exists in the Webhook API component of WSO2 API management products, where HTTP request headers from user input are reflected into HTTP responses without proper validation or sanitization. This is a classic header injection vulnerability (CWE-74: Improper Neutralization of Special Elements used in an Output Command) that occurs when user-controlled data is passed unsanitized into HTTP response construction logic. The affected products are all part of WSO2's API management and gateway suite, which process HTTP requests through gateway and management components. The root cause is insufficient input filtering before header values are written to HTTP response streams, allowing attackers to inject newline characters (CR/LF) and additional headers.
RemediationAI
Apply the vendor-released patch from WSO2 security advisory WSO2-2025-4410 (https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4410/) which includes input validation and sanitization fixes for Webhook API header handling. Exact patched version numbers must be obtained from the advisory; upgrade all affected products (API Manager, Universal Gateway, Traffic Manager, API Control Plane, Carbon API Gateway, and Carbon API Management Implementation) to the fixed release. If immediate patching is not possible, restrict Webhook API access to trusted internal networks and authenticated callers only via network segmentation or API gateway access controls, which will limit exposure but may impact functionality for legitimate external webhook integrations. Consider implementing a Web Application Firewall (WAF) rule to detect and block HTTP requests containing encoded newline characters (\r, \n, %0d, %0a) in headers sent to Webhook endpoints, with the trade-off that this may block legitimate requests with special characters in header values.
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,
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
Predictable HMAC shared secrets generated by the API Publisher component of WSO2 API Manager allow a sophisticated attac
The XML parsers within multiple WSO2 products accept user-supplied XML data without properly configuring to prevent the
Role-based access control bypass in WSO2 API Manager 3.x allows authenticated users with the 'Internal/Everyone' role to
Reflected cross-site scripting across at least eight WSO2 platform products - including Identity Server, API Manager, AP
The authentication endpoint fails to adequately validate user-supplied input before reflecting it back in the response.
Reflected cross-site scripting in the authentication endpoint of WSO2 API Manager and Identity Server allows unauthentic
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today