CVE-2025-8154
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Webhook API component accepts user-supplied input for HTTP request headers without proper validation or sanitization, enabling HTTP Response Header Injection (CRLF injection). Attackers can inject arbitrary headers into responses, leading to cache poisoning, security header bypass, and cookie injection for potential session hijacking.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.5.0, < 4.5.0.21>= 4.1.0, < 4.1.0.218>= 4.2.0, < 4.2.0.164>= 4.3.0, < 4.3.0.74>= 4.4.0, < 4.4.0.38>= 4.5.0, < 4.5.0.20>= 4.5.0, < 4.5.0.19>= 4.5.0, < 4.5.0.19CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify WSO2 product and versionLocate the product-info.xml file in the WSO2 installation directory (typically in the root or conf directory), or access the Management Console and navigate to About > Version. Alternatively, check the product-specific banner or README file in the installation root.Affected if The installed version falls within any of the affected ranges: API Control Plane >= 4.5.0 and < 4.5.0.21; API Manager 4.1.0 to < 4.1.0.218, 4.2.0 to < 4.2.0.164, 4.3.0 to < 4.3.0.74, 4.4.0 to < 4.4.0.38, or 4.5.0 to < 4.5.0.20; Traffic Manager >= 4.5.0 and < 4.5.0.19; Universal Gateway >= 4.5.0 and
-
Confirm Webhook API component is enabledCheck the WSO2 deployment.toml configuration file (located in the repository/conf directory) for the webhook receiver configuration. Look for sections containing 'webhook' or 'eventHub' related configurations. Alternatively, check if the WebAPI WAR file is deployed in the repository/deployment/server/webapps directory.Affected if The Webhook API component is deployed and enabled in the WSO2 environment
-
Identify external exposure of Webhook APIReview API Gateway configurations and check if the Webhook API endpoints are exposed externally. Examine the repository/conf/api-manager.xml file and any custom API sequences for routes targeting webhook functionality. Check the API Manager Store or Publisher for any published Webhook APIs.Affected if The Webhook API is accessible from outside the trusted network or exposed via the API Gateway
-
Review recent access logs for suspicious header injectionExamine WSO2 access logs (located in repository/logs/http_access_<date>.log) for requests to webhook endpoints containing CRLF sequences (search for %0D%0A, \r\n, or raw newlines in header values) or unusual header patterns that could indicate testing or exploitation.Affected if Log analysis reveals malformed requests with injected headers targeting webhook endpoints
The environment is affected if it runs any of the listed WSO2 products within the specified version ranges AND has the Webhook API component enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.1.0.2184.2.0.1644.3.0.74
Implement strict input validation and output encoding for all header values, using allowlists for permitted headers and escaping or rejecting special characters (particularly CRLF sequences) to prevent header injection.
Api Control Plane: 4.5.0.21+ | Api Manager: 4.1.0.218+, 4.2.0.164+, 4.3.0.74+, or 4.4.0.38+ | Traffic Manager: 4.5.0.19+ | Universal Gateway: 4.5.0.19+
- 1. Identify the specific WSO2 product (Api Control Plane, Api Manager, Traffic Manager, or Universal Gateway) currently deployed
- 2. Determine the exact currently-installed version by checking the product's version file or administrative console
- 3. For Api Control Plane: upgrade to version 4.5.0.21 or later
- 4. For Api Manager: upgrade to version 4.1.0.218 or later (for 4.1.x), 4.2.0.164 or later (for 4.2.x), 4.3.0.74 or later (for 4.3.x), or 4.4.0.38 or later (for 4.4.x)
- 5. For Traffic Manager: upgrade to version 4.5.0.19 or later
- 6. For Universal Gateway: upgrade to version 4.5.0.19 or later
- 7. Obtain the upgrade package from the official WSO2 distribution repository (https://wso2.com/api-management/ or https://wso2.com/)
- 8. Test the upgrade in a non-production environment first
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8154 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8154 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data