dbcve.org
Enterprise IntegratorApplication · Wso2

CVE-2022-39810

MEDIUM · 6.1 CVSS v3.1 Published 2022-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
High EPSS Remotely reachable 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
An issue was discovered in WSO2 Enterprise Integrator 6.4.0. A Reflected Cross-Site Scripting (XSS) vulnerability has been identified in the Management Console under /carbon/ndatasource/validateconnection/ajaxprocessor.jsp via the driver parameter. Session hijacking or similar attacks would not be 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 Enterprise Integrator 6.4.0's Management Console. The vulnerability is located in the /carbon/ndatasource/validateconnection/ajaxprocessor.jsp endpoint, where the 'driver' parameter is not properly sanitized before being reflected back in the response. This allows an attacker to inject malicious JavaScript through a crafted URL.

MitigationImplement proper input validation and output encoding for the 'driver' parameter in the affected JSP file. Consider applying WSO2 security patches if available.

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
Enterprise IntegratorApplication
Affected:= 6.4.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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/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 WSO2 Enterprise Integrator installation
    Locate the WSO2 EI installation directory and check for the product information file or startup scripts. Run: find / -name 'wso2server.sh' -o -name 'carbon.sh' 2>/dev/null or check common paths like /opt/wso2/, /usr/local/wso2/, or C:\Program Files\wso2\
    Affected if WSO2 Enterprise Integrator is installed on the system
  2. Confirm installed version is 6.4.0
    Check the product version file or the Management Console login page. Common locations: <install_dir>/repository/components/plugins/ for version info, or access the Management Console at https://localhost:9443/carbon/ and view the About page
    Affected if The installed version equals exactly 6.4.0
  3. Verify Management Console is accessible
    Attempt to access the Management Console at the default URL: https://localhost:9443/carbon/ or the configured host/port. Check if the console responds to HTTP/HTTPS requests
    Affected if The Management Console is reachable and responds to requests
  4. Confirm vulnerable endpoint exists
    Check if the ajaxprocessor.jsp file exists at /carbon/ndatasource/validateconnection/ajaxprocessor.jsp within the WSO2 installation. On the filesystem, search for: find <install_dir> -path '*/carbon/ndatasource/validateconnection/ajaxprocessor.jsp'
    Affected if The file carbon/ndatasource/validateconnection/ajaxprocessor.jsp exists in the installation

You are affected if WSO2 Enterprise Integrator version 6.4.0 is installed with the Management Console accessible and the vulnerable ajaxprocessor.jsp endpoint is present.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for the 'driver' parameter in the affected JSP file. Consider applying WSO2 security patches if available.

Recommended fix Moderate confidence

WSO2 Enterprise Integrator 6.5.0 or later

  1. 1. Identify all WSO2 Enterprise Integrator 6.4.0 deployments in your environment
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Perform a full backup of the current installation including configuration files and databases
  4. 4. Download WSO2 Enterprise Integrator from the official WSO2 repository (https://wso2.com/integration/)
  5. 5. Upgrade to a version higher than 6.4.0 (WSO2 EI 6.5.0 or later recommended)
  6. 6. Migrate custom configurations from the old installation to the new version
  7. 7. Test all critical integration workflows after migration
  8. 8. Verify the XSS vulnerability is resolved by attempting to inject script via the /carbon/ndatasource/validateconnection/ajaxprocessor.jsp driver parameter
Caveat Review WSO2 migration guides for configuration changes between 6.4.0 and target version; custom mediators and datasources may require reconfiguration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Integrator 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-2022-39810 — 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-2022-39810 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