Multiple WSO2 products have been identified as vulnerable due to improper output encoding, a Stored Cross Site Scripting (XSS) attack can be
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.40% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: org.wso2.carbon.registry:carbon-registry (Maven) 4.7.37.
Low priority for now. Upgrade to org.wso2.carbon.registry:carbon-registry (Maven) 4.7.37 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Multiple WSO2 products have been identified as vulnerable due to improper output encoding, a Stored Cross Site Scripting (XSS) attack can be carried out by an attacker injecting a malicious payload into the Registry feature of the Management Console.
- Published
- Dec 18, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 33th percentile
- CWE
- CWE-79
Report tools
Action score
19
Monitor
Low priority for now.
- CVSS
- 19 / 40 · 4.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- 4.8
- CNA · WSO2
- 4.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wso2 | api manager | cpe:2.3:a:wso2:api_manager |
| wso2 | api manager analytics | cpe:2.3:a:wso2:api_manager_analytics |
| wso2 | api microgateway | cpe:2.3:a:wso2:api_microgateway |
| wso2 | data analytics server | cpe:2.3:a:wso2:data_analytics_server |
| wso2 | enterprise integrator | cpe:2.3:a:wso2:enterprise_integrator |
| wso2 | identity server as key manager | cpe:2.3:a:wso2:identity_server_as_key_manager |
| wso2 | identity server | cpe:2.3:a:wso2:identity_server |
| wso2 | identity server analytics | cpe:2.3:a:wso2:identity_server_analytics |
| wso2 | message broker | cpe:2.3:a:wso2:message_broker |
Limit the impact of XSS
This is a cross-site scripting (XSS) vulnerability. A well-configured Content-Security-Policy doesn't fix it, but greatly reduces its impact. Check your site's CSP and other security headers for free.
Check security headersAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wso2 api manager2.2.0
- wso2 api manager2.5.0
- wso2 api manager2.6.0
- wso2 api manager3.0.0
- wso2 api manager3.1.0
- wso2 api manager3.2.0
- wso2 api manager analytics2.2.0
- wso2 api manager analytics2.5.0
- wso2 api microgateway2.2.0
- wso2 data analytics server3.2.0
- wso2 enterprise integrator6.1.0
- wso2 enterprise integrator6.1.1
- wso2 enterprise integrator6.2.0
- wso2 enterprise integrator6.3.0
- wso2 enterprise integrator6.4.0
- wso2 enterprise integrator6.5.0
- wso2 enterprise integrator6.6.0
- wso2 identity server5.10.0
- wso2 identity server5.4.0
- wso2 identity server5.4.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.
WSO2 WSO2 API Manager
- before 2.2.0.0unknown
- 2.2.0.0 and later · before 2.2.0.1affected
- 2.5.0.0 and later · before 2.5.0.1affected
- 2.6.0.0 and later · before 2.6.0.1affected
- 3.0.0.0 and later · before 3.0.0.1affected
- 3.1.0.0 and later · before 3.1.0.1affected
- 3.2.0.0 and later · before 3.2.0.1affected
WSO2 WSO2 API Manager Analytics
- before 2.2.0.0unknown
- 2.2.0.0 and later · before 2.2.0.1affected
- 2.5.0.0 and later · before 2.5.0.1affected
WSO2 WSO2 API Microgateway
- before 2.2.0.0unknown
- 2.2.0.0 and later · before 2.2.0.1affected
WSO2 WSO2 Data Analytics Server
- before 3.2.0.0unknown
- 3.2.0.0 and later · before 3.2.0.1affected
WSO2 WSO2 Enterprise Integrator
- before 6.1.0.0unknown
- 6.1.0.0 and later · before 6.1.0.9affected
- 6.1.1.0 and later · before 6.1.1.9affected
- 6.2.0.0 and later · before 6.2.0.7affected
- 6.3.0.0 and later · before 6.3.0.1affected
- 6.4.0.0 and later · before 6.4.0.1affected
- 6.5.0.0 and later · before 6.5.0.6affected
- 6.6.0.0 and later · before 6.6.0.11affected
WSO2 WSO2 Identity Server
- before 5.4.0.0unknown
- 5.4.0.0 and later · before 5.4.0.4affected
- 5.4.1.0 and later · before 5.4.1.3affected
- 5.5.0.0 and later · before 5.5.0.1affected
- 5.6.0.0 and later · before 5.6.0.1affected
- 5.7.0.0 and later · before 5.7.0.1affected
- 5.8.0.0 and later · before 5.8.0.5affected
- 5.9.0.0 and later · before 5.9.0.1affected
- 5.10.0.0 and later · before 5.10.0.1affected
WSO2 WSO2 Identity Server Analytics
- before 5.4.0.0unknown
- 5.4.0.0 and later · before 5.4.0.2affected
- 5.4.1.0 and later · before 5.4.1.2affected
- 5.5.0.0 and later · before 5.5.0.1affected
- 5.6.0.0 and later · before 5.6.0.1affected
WSO2 WSO2 IS as Key Manager
- before 5.5.0.0unknown
- 5.5.0.0 and later · before 5.5.0.1affected
- 5.6.0.0 and later · before 5.6.0.1affected
- 5.7.0.0 and later · before 5.7.0.1affected
- 5.9.0.0 and later · before 5.9.0.1affected
- 5.10.0.0 and later · before 5.10.0.1affected
WSO2 WSO2 Message Broker
- before 3.2.0.0unknown
- 3.2.0.0 and later · before 3.2.0.3affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.wso2.carbon.registry:carbon-registry | before 4.7.37 | 4.7.37 |
Same product
wso2: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-29464Certain WSO2 products allow unrestricted file upload with resultant remote code execution.KEV99Now
- CVE-2020-24589The Management Console in WSO2 API Manager through 3.1.0 and API Microgateway 2.2.0 allows XML External Entity injection (XXE) attacks.44Plan
- CVE-2026-2053Unauthenticated Server-Side Request Forgery via WS-Addressing in WSO2 API Manager40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-6838Dec 15, 2023 · Reflected XSS vulnerability can be exploited by tampering a request parameter in Authentication Endpoint.24Monitor
- ← EarlierCVE-2023-6839Dec 15, 2023 · Due to improper error handling, a REST API resource could expose a server side error containing an internal WSO2 specific package name in th21Monitor
- Later →CVE-2024-2321Feb 27, 2025 · Incorrect Authorization in Multiple WSO2 Products Allows API Access via Refresh Token22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.wso2.carbon.registry:carbon-registry | 4.7.37 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-68383 days apartReflected XSS vulnerability can be exploited by tampering a request parameter in Authentication Endpoint.24Monitor
- CVE-2023-31664210 days apartA reflected cross-site scripting (XSS) vulnerability in /authenticationendpoint/login.do of WSO2 API Manager before 4.2.0 allows attackers t24Monitor
- CVE-2024-5848437 days apartReflected Cross-Site Scripting (XSS) in Multiple WSO2 Products Due to Improper Input Validation24Monitor
- CVE-2024-5962521 days apartReflected Cross-Site Scripting (XSS) in Authentication Endpoint of Multiple WSO2 Products Due to Missing Output Encoding24Monitor
- CVE-2024-8008532 days apartReflected Cross-Site Scripting (XSS) in Multiple WSO2 Products via JDBC User Store Connection Validation20Monitor
- CVE-2024-3509532 days apartStored Cross-Site Scripting (XSS) in Management Console of Multiple WSO2 Products via Rich Text Editor17Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
nvd-primary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.