Cross-Site Scripting via HTML Sanitization in WSO2 Publisher and Developer Portals Allows Malicious Script Execution
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.5.0.55, 4.6.0.19, 3.2.0.470, 3.2.1.89, 4.1.0.254, and 5 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Insufficient HTML sanitization in the Publisher Portal and Developer Portal allows untrusted user input to be rendered without proper encoding or neutralization. This enables the injection and execution of malicious JavaScript when affected API documents are viewed. Successful exploitation may result in the execution of malicious scripts within the user's browser context when viewing API documentation. Users with permissions to access the API documentation through these portals may be impacted, potentially allowing attackers to perform actions on behalf of the user, depending on their session privileges.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- WSO2 WSO2 API Control Plane
From 4.5.0 · fixed in 4.5.0.55; From 4.6.0 · fixed in 4.6.0.19
- WSO2 WSO2 API Manager
From 3.2.0 · fixed in 3.2.0.470; From 3.2.1 · fixed in 3.2.1.89; From 4.1.0 · fixed in 4.1.0.254; From 4.2.0 · fixed in 4.2.0.194; From 4.3.0 · fixed in 4.3.0.105; From 4.4.0 · fixed in 4.4.0.69; From 4.5.0 · fixed in 4.5.0.54; From 4.6.0 · fixed in 4.6.0.18