CVE-2024-8008VulnerabilityPublished 2 Jun 2025Updated 16 Oct 2026

CVE-2024-8008: WSO2 Enterprise Integrator · XSS or 'Cross-site Scripting'

Affects WSO2 Enterprise IntegratorSource CVE Database V5

Not known to be exploited · CVSS 5.2 Medium : upgrade to 6.6.0.211 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.2Medium

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.6.0.211, 4.5.0.16, 4.4.0.1 +28

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

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to 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 2 Jun 2025
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 2026-10-25.

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 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.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
WSO2WSO2 Enterprise Integrator	Affected >=6.6.0 <6.6.0.211	Fixed in 6.6.0.211
WSO2WSO2 API Manager	Affected >=3.1.0 <3.1.0.305 >=3.2.0 <3.2.0.396 >=3.2.1 <3.2.1.28 >=4.0.0 <4.0.0.313 >=4.1.0 <4.1.0.182 >=4.2.0 <4.2.0.121 >=4.3.0 <4.3.0.32 >=4.4.0 <4.4.0.1 >=4.5.0 <4.5.0.16	Fixed in 4.5.0.16 4.4.0.1 4.3.0.32 4.2.0.121 4.1.0.182 4.0.0.313 3.2.1.28 3.2.0.396 3.1.0.305
WSO2WSO2 Identity Server as Key Manager	Affected >=5.10.0 <5.10.0.321	Fixed in 5.10.0.321
WSO2WSO2 Identity Server	Affected >=5.10.0 <5.10.0.328 >=5.11.0 <5.11.0.374 >=6.0.0 <6.0.0.216 >=6.1.0 <6.1.0.201 >=7.0.0 <7.0.0.69	Fixed in 7.0.0.69 6.1.0.201 6.0.0.216 5.11.0.374 5.10.0.328
WSO2WSO2 Open Banking IAM	Affected >=2.0.0 <2.0.0.374	Fixed in 2.0.0.374
WSO2WSO2 Open Banking AM	Affected >=2.0.0 <2.0.0.354	Fixed in 2.0.0.354
WSO2WSO2 Traffic Manager	Affected >=4.5.0 <4.5.0.16	Fixed in 4.5.0.16
WSO2WSO2 API Control Plane	Affected >=4.5.0 <4.5.0.17	Fixed in 4.5.0.17
WSO2WSO2 Universal Gateway	Affected >=4.5.0 <4.5.0.16	Fixed in 4.5.0.16
WSO2WSO2 Carbon Identity User Store Configuration UI	Affected >=5.14.127 <5.14.127.9 >=5.17.5 <5.17.5.289 >=5.17.118 <5.17.118.10 >=5.18.187 <5.18.187.276 >=5.18.248 <5.18.248.22 >=5.23.8 <5.23.8.193 >=5.24.8 <5.24.8.11 >=5.25.92 <5.25.92.104 >=5.25.705 <5.25.705.10 >=5.25.713 <5.25.713.1 >=5.25.724 <5.25.724.1 >=7.0.78 <7.0.78.46	Fixed in 7.0.78.46 5.25.724.1 5.25.713.1 5.25.705.10 5.25.92.104 5.24.8.11 5.23.8.193 5.18.248.22 5.18.187.276 5.17.118.10 5.17.5.289 5.14.127.9
Mavenorg.wso2/integrator`pkg:maven/org.wso2/integrator`Other threats	Affected =6.6.0	Fixed in–

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

AI-suggested

2) Implement strict input validation and output encoding on all user-supplied data, especially in error messages and diagnostic outputs related to JDBC user store connection validation. 3) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS payloads. 4) Conduct thorough security testing, including automated and manual penetration testing focused on XSS vectors in the affected product interfaces. 5) Educate users and administrators about the risks of clicking untrusted links or submitting suspicious requests to the integration platform. 6) Monitor logs and network traffic for unusual or suspicious activities that could indicate exploitation attempts. 7) Consider deploying Web Application Firewalls (WAFs) with rules tailored to detect and block reflected XSS payloads targeting WSO2 endpoints. These steps go beyond generic advice by focusing on the specific context of the JDBC user store connection validation error messages and the operational environment of WSO2 Enterprise Integrator.

Description

A reflected cross-site scripting (XSS) vulnerability exists in multiple WSO2 products due to insufficient output encoding in error messages generated by the JDBC user store connection validation request. A malicious actor can inject a specially crafted payload into the request, causing the browser to execute arbitrary JavaScript in the context of the vulnerable page. This vulnerability may allow UI manipulation, redirection to malicious websites, or data exfiltration from the browser. However, since all session-related sensitive cookies are protected with the httpOnly flag, session hijacking is not possible.

Impact

For European organizations, this vulnerability could lead to unauthorized manipulation of user interface elements, phishing through redirection to malicious sites, and exfiltration of sensitive information accessible in the browser context. Although session hijacking is mitigated, the ability to execute arbitrary scripts can undermine user trust and lead to data leakage or further social engineering attacks. Organizations relying on WSO2 Enterprise Integrator for critical integration workflows may face operational disruptions if attackers exploit this vulnerability to mislead users or extract confidential data. The impact is particularly significant for sectors with stringent data protection requirements such as finance, healthcare, and government, where data confidentiality and integrity are paramount. Additionally, the reflected XSS could be used as a stepping stone for more complex attacks targeting internal systems or users with elevated privileges. The medium severity rating suggests that while the vulnerability is not immediately critical, it warrants timely remediation to prevent exploitation in targeted attacks.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2025/WSO2-2024-3178/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Oct 2025, 06:14 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats