Browser script execution via unencoded request parameters
Published Dec 15, 2022 · Updated Aug 3, 2024
Cross-site scripting in WSO2 Carbon Registry before 4.8.7 allows remote authenticated users to run script in another user's browser. Six registry-profile JSP handlers read parentPath, path, username, or profile_menu request parameters and use them without HTML encoding. Access to the profile interface and victim interaction are required, and the resulting script can alter management-console content in the victim's browser.
Summary
What happened
Cross-site scripting in WSO2 Carbon Registry before 4.8.7 allows remote authenticated users to run script in another user's browser. Six registry-profile JSP handlers read parentPath, path, username, or profile_menu request parameters and use them without HTML encoding. Access to the profile interface and victim interaction are required, and the resulting script can alter management-console content in the victim's browser.
The record
- CVE
- CVE-2022-4521
- Published
- Dec 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- WSO2
- Product
- WSO2 Carbon Registry
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 15, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.8.0
- Affected versionversion=4.8.1
- Affected versionversion=4.8.2
- Affected versionversion=4.8.3
- Affected versionversion=4.8.4
- Affected versionversion=4.8.5
- Affected versionversion=4.8.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo