CVE-2025-8154VulnerabilityPublished 11 May 2026

In Webhook API invocations, the component accepts user-supplied input for HTTP request headers without sufficient

Source GCVE Database

Authoritative record:CVE-2025-8154· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in 4.5.0.20 : update WSO2 API Manager when convenient.

Data as of 27 Oct 2026, 01:31 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 4.5.0.20, 4.4.0.38, 4.3.0.74 +9

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-j72f-vgmh-c8hr

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
WSO2WSO2 API Manager	Affected >=4.5.0 <4.5.0.20	Fixed in 4.5.0.20
WSO2WSO2 API Manager	Affected >=4.4.0 <4.4.0.38	Fixed in 4.4.0.38
WSO2WSO2 API Manager	Affected >=4.3.0 <4.3.0.74	Fixed in 4.3.0.74
WSO2WSO2 API Manager	Affected >=4.2.0 <4.2.0.164	Fixed in 4.2.0.164
WSO2WSO2 API Manager	Affected >=4.1.0 <4.1.0.218	Fixed in 4.1.0.218
WSO2WSO2 Universal Gateway	Affected >=4.5.0 <4.5.0.19	Fixed in 4.5.0.19

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should consider implementing input validation and sanitization on user-supplied HTTP headers in Webhook API invocations as a temporary mitigation.

Description

This vulnerability involves insufficient validation or sanitization of user-supplied input for HTTP request headers in Webhook API invocations, allowing injection of arbitrary HTTP response headers. Exploitation can lead to manipulation of browser caching, alteration of security headers, and injection of sensitive information such as cookies, potentially enabling session hijacking or other malicious actions.

Impact

An attacker can inject or overwrite HTTP response headers, potentially manipulating browser caching behavior, altering security headers, and exposing sensitive information such as cookies. This can lead to session hijacking or other malicious activities. The CVSS score is 5.3 (medium severity), indicating a moderate impact with no confidentiality loss but integrity impact.

Summary

The Webhook API component accepts user-supplied input for HTTP request headers without adequate validation or sanitization. This flaw permits attackers to inject or overwrite arbitrary HTTP response headers. Such manipulation can affect browser caching policies, security-related headers, and expose sensitive data like cookie values, which may facilitate session hijacking or other malicious activities. The vulnerability is identified as CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component).

CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements
Programming languages and supporting technologies might be chosen which are not subject to these issues.
Implementation
Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Server Side Include (SSI) Injection (opens in a new tab)
HTTP Request Splitting (opens in a new tab)
Command Line Execution through SQL Injection (opens in a new tab)
Double Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Oct 2026, 01:31 UTC

WeaknessesCWE-74

Technical details

References

Community reviews

Related threats