XWiki Platform 13.10.7/14.4.1/14.5RC1 cross-site request forgery
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability has been found in XWiki Platform 13.10.7/14.4.1/14.5RC1 (Content Management System) and classified as problematic. This vulnerability affects an unknown function. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity. CVE summarizes:
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 ```
The weakness was disclosed 11/24/2022 as GHSA-mq7h-5574-hw9f. The advisory is shared for download at github.com. This vulnerability was named CVE-2022-41927 since 09/30/2022. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available.
Applying the patch 7fd4cda0590180c4d34f557597e9e10e263def9e is able to eliminate this problem. The bugfix is ready for download at github.com.
CVSSv3VulDB Meta Base Score: 5.8
VulDB Meta Temp Score: 5.7
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.4
CNA Vector (GitHub, Inc.): 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Cross-site request forgery
CWE: CWE-352 / CWE-862 / CWE-863
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Timeline09/30/2022 CVE reserved
11/24/2022 +55 days Advisory disclosed
11/24/2022 +0 days VulDB entry created
11/24/2022 +0 days VulDB last update
CVE: CVE-2022-41927 (🔒)
EntryCreated: 11/24/2022 09:33 AM
Changes: 11/24/2022 09:33 AM (52)
Do you know our Splunk app?
Download it now for free!