dbcve.org
Api ManagerApplication · Wso2

CVE-2024-8008

MEDIUM · 5.2 CVSS v3.1 Published 2025-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
No privileges

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

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 · high confidence

A reflected cross-site scripting (XSS) vulnerability exists in WSO2 products where error messages from JDBC user store connection validation requests do not properly encode output. Attackers can inject malicious JavaScript payloads into requests that get reflected back in unencoded error responses, allowing execution in user browsers.

MitigationImplement proper output encoding on all error messages generated by the JDBC user store connection validation functionality to neutralize XSS payloads in user-controlled input.

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
Api ManagerApplication
Affected:= 3.1.0= 3.2.0= 3.2.1= 4.0.0= 4.1.0= 4.2.0= 4.3.0
Enterprise IntegratorApplication
Affected:= 6.6.0
Identity ServerApplication
Affected:= 5.10.0= 5.11.0= 6.0.0= 6.1.0= 7.0.0
Identity Server As Key ManagerApplication
Affected:= 5.10.0
Open Banking AmApplication
Affected:= 2.0.0
Open Banking IamApplication
Affected:= 2.0.0

CVSS 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
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed WSO2 product
    Check the product name in the installation directory or by accessing the management console. Common locations: <installation>/bin/wso2server.sh or check the welcome/page of the management console.
    Affected if The product is one of: API Manager, Enterprise Integrator, Identity Server, Identity Server As Key Manager, Open Banking AM, or Open Banking IAM.
  2. Determine the installed product version
    Check the product version from the management console footer, or in the <installation>/bin/wso2server.sh script, or in the <installation>/repository/components/plugins directory for version information.
    Affected if The version matches: API Manager 3.1.0, 3.2.0, 3.2.1, 4.0.0, 4.1.0, 4.2.0, or 4.3.0; Enterprise Integrator 6.6.0; Identity Server 5.10.0, 5.11.0, 6.0.0, 6.1.0, or 7.0.0; Identity Server As Key Manager 5.10.0; Open Banking AM 2.0.0; or Open Banking IAM 2.0.0.
  3. Check if JDBC user store is configured
    Examine the user-mgt.xml configuration file in <installation>/repository/conf directory. Look for the UserStoreManager class configuration. If it uses org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager, JDBC user store is in use.
    Affected if The primary or secondary user store is configured to use JDBCUserStoreManager (org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager).
  4. Verify access to JDBC user store connection validation
    Access the user store configuration section in the WSO2 management console or API. The connection validation feature is typically available under User Store > Configuration in the management console.
    Affected if The user has access to configure or test JDBC user store connections in the WSO2 management interface.

The environment is affected if it runs any of the listed WSO2 product versions AND uses JDBC user store configuration, because the XSS vulnerability exists specifically in the JDBC user store connection validation error responses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper output encoding on all error messages generated by the JDBC user store connection validation functionality to neutralize XSS payloads in user-controlled input.

Fix this in Api Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8008 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8008 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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