Skip to content

Incorrect Use of Privileged APIs in org.xwiki.platform.skin.skinx

Moderate severity GitHub Reviewed Published Apr 8, 2022 in xwiki/xwiki-platform • Updated Jan 27, 2023

Package

maven org.xwiki.platform:xwiki-platform-skin-skinx (Maven)

Affected versions

>= 13.5.0, < 13.10
< 12.10.11
>= 13.0.0, < 13.4.6

Patched versions

13.10
12.10.11
13.4.6

Description

Impact

Simple users can create global SSX/JSX without specific rights: in theory only users with Programming Rights should be allowed to create SSX or JSX that are executed everywhere on a wiki. But a bug allow anyone with edit rights to actually create those.

Patches

This issue has been patched in XWiki 13.10-rc-1, 12.10.11 and 13.4.6.

Workarounds

There's no easy workaround for this issue, administrators should upgrade their wiki.

References

https://jira.xwiki.org/browse/XWIKI-19155

For more information

If you have any questions or comments about this advisory:

References

@surli surli published to xwiki/xwiki-platform Apr 8, 2022
Published by the National Vulnerability Database Apr 8, 2022
Published to the GitHub Advisory Database Apr 8, 2022
Reviewed Apr 8, 2022
Last updated Jan 27, 2023

Severity

Moderate

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
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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:R/S:C/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(45th percentile)

Weaknesses

CVE ID

CVE-2022-24821

GHSA ID

GHSA-ghcq-472w-vf4h

Source code

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