CVE-2022-34323 Cross-site scripting in n/a
Authenticated attackers can inject JavaScript via stored XSS in filter, display, and alert names, potentially compromising other users' sessions.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2022-34323?
CVE-2022-34323 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
Multiple XSS issues were discovered in Sage XRT Business Exchange 12.4.302 that allow an attacker to execute JavaScript code in the context of other users' browsers. The attacker needs to be authenticated to reach the vulnerable features. An issue is present in the Filters and Display model features (OnlineBanking > Web Monitoring > Settings > Filters / Display models). The name of a filter or a display model is interpreted as HTML and can thus embed JavaScript code, which is executed when displayed. This is a stored XSS. Another issue is present in the Notification feature (OnlineBanking > Configuration > Notifications and alerts > Alerts *). The name of an alert is interpreted as HTML, and can thus embed JavaScript code, which is executed when displayed. This is a stored XSS. (Also, an issue is present in the File download feature, accessible via /OnlineBanking/cgi/isapi.dll/DOWNLOADFRS. When requesting to show the list of downloadable files, the contents of three form fields are embedded in the JavaScript code without prior sanitization. This is essentially a self-XSS.)
Weakness: CWE-79
Which versions are affected by CVE-2022-34323?
It affects 1 product.
Products include Sage Sage Xrt Business Exchange.
How do I fix CVE-2022-34323?
No fix has been published for CVE-2022-34323 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2022-34323 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-34323 exists.
Other vulnerabilities in n/a
Sources
Also known as GHSA-g8g2-px5g-7jq3.