CVE-2021-42646 json
XML External Entity (XXE) vulnerability in the file based service provider creation feature of the Management Console in WSO2 API Manager 2…
published 4y ago modified 4mo ago also EUVD-2021-29610
- cvss
- 9.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.8%
- EPSS 3.8% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
XML External Entity (XXE) vulnerability in the file based service provider creation feature of the Management Console in WSO2 API Manager 2.6.0, 3.0.0, 3.1.0, 3.2.0, and 4.0.0; and WSO2 IS as Key Manager 5.7.0, 5.9.0, and 5.10.0; and WSO2 Identity Server 5.7.0, 5.8.0, 5.9.0, 5.10.0, and 5.11.0. Allows attackers to gain read access to sensitive information or cause a denial of service via crafted GET requests.
Patch / fix
- github.com/wso2/carbon-identity-framework#3472 pull request
Is CVE-2021-42646 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
3.76% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:N/A:P |
Classification
- Weakness
-
- CWE-611 Improper Restriction of XML External Entity Reference
References
-
github.com
/wso2/carbon-identity-framework/pull/3472
patch, third-party-advisory
-
seclists.org
/fulldisclosure/2022/Jun/7
mailing-list, third-party-advisory
-
packetstormsecurity.com
/files/167465/WSO2-Management-Console-XML-Injection.html
third-party-advisory, vdb-entry
- security.docs.wso2.com /en/latest/security-announcements/security-advisories/2021/WSO2-2021-1289/
Sources
- CVE List CVE-2021-42646
- NVD CVE-2021-42646
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.