Skip to content

XWiki Platform vulnerable to privilege escalation (PR) from account through like LiveTableResults

Critical severity GitHub Reviewed Published Jun 20, 2023 in xwiki/xwiki-platform • Updated Nov 12, 2023

Package

maven org.xwiki.platform:xwiki-platform-like-ui (Maven)

Affected versions

>= 12.9-rc-1, < 14.4.8
>= 14.5, < 14.10.6
>= 15.0-rc-1, < 15.1

Patched versions

14.4.8
14.10.6
15.1

Description

Impact

Any logged in user can add dangerous content in their first name field and see it executed with programming rights. Leading to rights escalation.

Patches

The vulnerability has been fixed on XWiki 14.4.8, 14.10.6, and 15.1.

Workarounds

The vulnerability can be fixed by applying this patch.

On versions before 13.4-rc-1, the fix needs to be applied on XWiki.Like.Code.LiveTableResultPage.

References

For more information

If you have any questions or comments about this advisory:

References

@manuelleduc manuelleduc published to xwiki/xwiki-platform Jun 20, 2023
Published to the GitHub Advisory Database Jun 20, 2023
Reviewed Jun 20, 2023
Published by the National Vulnerability Database Jun 23, 2023
Last updated Nov 12, 2023

Severity

Critical

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
Low
User interaction
None
Scope
Changed
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:L/UI:N/S:C/C:H/I:H/A:H

EPSS score

0.206%
(59th percentile)

Weaknesses

CVE ID

CVE-2023-35152

GHSA ID

GHSA-rf8j-q39g-7xfm

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.