First published: Wed Nov 23 2022(Updated: )
XWiki Platform is vulnerable to Cross-Site Request Forgery (CSRF) that may allow attackers to delete or rename tags without needing any confirmation. The problem has been patched in XWiki 13.10.7, 14.4.1 and 14.5RC1. Workarounds: It's possible to patch existing instances directly by editing the page Main.Tags and add this kind of check, in the code for renaming and for deleting: ``` #if (!$services.csrf.isTokenValid($request.get('form_token'))) #set ($discard = $response.sendError(401, "Wrong CSRF token")) #end ```
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Xwiki | >3.2<13.10.7 | |
Xwiki | =3.2-milestone2 | |
Xwiki | =3.2-milestone3 | |
Xwiki | =14.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2022-41927 is high with a severity value of 7.4.
CVE-2022-41927 affects XWiki Platform by allowing attackers to delete or rename tags without confirmation through Cross-Site Request Forgery (CSRF).
Versions between 3.2 and 13.10.7 as well as version 14.4 of XWiki are affected by CVE-2022-41927.
You can fix CVE-2022-41927 on your XWiki instance by updating to versions 13.10.7, 14.4.1, or 14.5RC1.
Yes, you can patch existing instances by editing the page directly.