CVE-2022-3573: Stored XSS in GitLab wiki changes page
- Vendors
- ABBGitLab
CVE-2022-3573 is a cross-site scripting vulnerability in GitLab CE and EE affecting all versions from 15.4 before 15.5.7, from 15.6 before 15.6.4, and from 15.7 before 15.7.2. The issue is caused by improper filtering of query parameters in the wiki changes page. Under affected conditions, an attacker can inject and execute arbitrary JavaScript in a victim’s browser when the crafted request is processed by a self-hosted GitLab instance that is not protected by a strict Content Security Policy. The flaw is client-side but can affect authenticated GitLab users interacting with the maliciously crafted page or link.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows arbitrary JavaScript execution in the context of the vulnerable GitLab instance. This can enable session hijacking, unauthorized actions on behalf of the victim, access to data visible to the victim within GitLab, interface manipulation, and delivery of further browser-based payloads. Impact depends on the privileges of the targeted user and whether an authenticated administrator or other high-privilege user can be induced to load the malicious content.
Mitigation
If you can’t patch tonight, do this now.
Where immediate patching is not possible, enforce a strict Content Security Policy on self-hosted GitLab instances to reduce the ability of injected JavaScript to execute. Additional temporary measures include restricting access to untrusted users, monitoring for suspicious requests targeting wiki change functionality, and limiting exposure of self-hosted instances until upgrades can be completed.
Remediation
Patch, then assume compromise.
Upgrade GitLab CE/EE to a fixed release. Patched versions include 15.5.7, 15.6.4, and 15.7.2 or later within the respective supported branches. Organizations running affected self-hosted instances should prioritize upgrading to a non-vulnerable version.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2022-3573 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2022-3573?
- Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2022-3573.
- Is there a patch for CVE-2022-3573?
- Upgrade GitLab CE/EE to a fixed release. Patched versions include 15.5.7, 15.6.4, and 15.7.2 or later within the respective supported branches.
- What products are affected by CVE-2022-3573?
- Gitlab and ABB Drive Composer.
- How severe is CVE-2022-3573?
- CVE-2022-3573 has a CVSS v3.1 score of 5.4 (Medium) and an EPSS score of 0.63% (51st percentile) as of Oct 16, 2026.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.