Skip to content

Cross-Site Request Forgery with QueryOnXWiki allows arbitrary database queries

High severity GitHub Reviewed Published Nov 20, 2023 in xwiki-contrib/application-admintools • Updated Nov 20, 2023

Package

maven org.xwiki.contrib:xwiki-application-admintools (Maven)

Affected versions

< 4.5.1

Patched versions

4.5.1

Description

Impact

A CSRF vulnerability in the query on XWiki tool allows executing arbitrary database queries on the database of the XWiki installation. Among other things, this allows modifying and deleting all data of the wiki. This could be both used to damage the wiki and to create an account with elevated privileges for the attacker, thus impacting the confidentiality, integrity and availability of the whole XWiki instance. A possible attack vector are comments on the wiki, by embedding an image with wiki syntax like [[image:path:/xwiki/bin/view/Admin/QueryOnXWiki?query=DELETE%20FROM%20xwikidoc]], all documents would be deleted from the database when an admin user views this comment.

Patches

This has been patched in Admin Tools Application 4.5.1 by adding form token checks.

Workarounds

The patch can also be applied manually to the affected pages. Alternatively, if the query tool is not needed, by deleting the document Admin.SQLToolsGroovy, all database query tools can be deactivated.

References

References

Published by the National Vulnerability Database Nov 20, 2023
Published to the GitHub Advisory Database Nov 20, 2023
Reviewed Nov 20, 2023
Last updated Nov 20, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.057%
(25th percentile)

Weaknesses

CVE ID

CVE-2023-48293

GHSA ID

GHSA-4f4c-rhjv-4wgv
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.