‼ CVE-2022-43799 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43809 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43800 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43814 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43818 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43830 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43797 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43828 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43827 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43825 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43821 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43829 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43823 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43826 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43822 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-43824 ‼
📖 Read
via "National Vulnerability Database".
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.📖 Read
via "National Vulnerability Database".
👍1
‼ CVE-2023-0028 ‼
📖 Read
via "National Vulnerability Database".
Cross-site Scripting (XSS) - Stored in GitHub repository linagora/twake prior to 2023.Q1.1200+.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-45027 ‼
📖 Read
via "National Vulnerability Database".
perfSONAR before 4.4.6, when performing participant discovery, incorrectly uses an HTTP request header value to determine a local address.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-37787 ‼
📖 Read
via "National Vulnerability Database".
An issue was discovered in WeCube platform 3.2.2. A DOM XSS vulnerability has been found on the plugin database execution page.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-40711 ‼
📖 Read
via "National Vulnerability Database".
PrimeKey EJBCA 7.9.0.2 Community allows stored XSS in the End Entity section. A user with the RA Administrator role can inject an XSS payload to target higher-privilege users.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-34322 ‼
📖 Read
via "National Vulnerability Database".
Multiple XSS issues were discovered in Sage Enterprise Intelligence 2021 R1.1 that allow an attacker to execute JavaScript code in the context of users' browsers. The attacker needs to be authenticated to reach the vulnerable features. An issue is present in the Notify Users About Modification menu and the Notifications feature. A user can send malicious notifications and execute JavaScript code in the browser of every user who has enabled notifications. This is a stored XSS, and can lead to privilege escalation in the context of the application. (Another issue is present in the Favorites tab. The name of a favorite or a folder of favorites is interpreted as HTML, and can thus embed JavaScript code, which is executed when displayed. This is a self-XSS.)📖 Read
via "National Vulnerability Database".