CVE-2022-39809
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 · uneditedAn 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/mediation_secure_vault/properties/ajaxprocessor.jsp via the name 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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in WSO2 Enterprise Integrator 6.4.0's Management Console at /carbon/mediation_secure_vault/properties/ajaxprocessor.jsp. The 'name' parameter is not properly sanitized, allowing injection of malicious script that executes in the victim's browser when the crafted link is accessed.
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= 6.4.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WSO2 Enterprise Integrator versionCheck the product version in the Management Console (typically under 'About' or via the /carbon/admin/about.jsp endpoint) or check the installation directory for version files. Compare against 6.4.0.Affected if The installed version is exactly 6.4.0
-
Confirm Management Console accessibilityVerify that the WSO2 Management Console is accessible by navigating to /carbon/ in the browser or checking if the endpoint responds. This is typically available on port 9443 by default.Affected if The Management Console is exposed and accessible (even if only on localhost)
-
Check mediation_secure_vault module availabilityAccess or probe the /carbon/mediation_secure_vault/ endpoint to confirm the mediation secure vault feature is enabled and accessible within the Management Console.Affected if The mediation_secure_vault feature is present and accessible in the Management Console
-
Identify vulnerable endpoint exposureConfirm the ajaxprocessor.jsp file exists at /carbon/mediation_secure_vault/properties/ajaxprocessor.jsp by accessing it or reviewing the deployed web application files in the carbon installation.Affected if The ajaxprocessor.jsp file exists at the vulnerable path and accepts a 'name' parameter without sanitization
You are affected if WSO2 Enterprise Integrator version 6.4.0 is running with the Management Console and mediation_secure_vault feature accessible, as the 'name' parameter in ajaxprocessor.jsp lacks proper input sanitization.
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.
From vendor dataImplement input validation and output encoding for the 'name' parameter in ajaxprocessor.jsp to neutralize malicious script payloads.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39809 — 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-2022-39809 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