Skip to content

The lesscss script service allows cache clearing without programming right

Low severity GitHub Reviewed Published Apr 29, 2025 in xwiki/xwiki-platform • Updated Apr 30, 2025

Package

maven org.xwiki.platform:xwiki-platform-lesscss-script (Maven)

Affected versions

>= 6.1-milestone-1, < 15.10.12
>= 16.0.0-rc-1, < 16.4.3
>= 16.5.0-rc-1, < 16.8.0-rc-1

Patched versions

15.10.12
16.4.3
16.8.0-rc-1

Description

Impact

The script API of the LESS compiler in XWiki is incorrectly checking for rights when calling the cache cleaning API, making it possible to clean the cache without having programming right. The only impact of this is a slowdown in XWiki execution as the caches are re-filled. As this vulnerability requires script right to exploit, and script right already allows unlimited execution of scripts, the additional impact due to this vulnerability is low.

Patches

This has been patched in XWiki 15.10.12, 16.4.3 and 16.8.0 RC1.

Workarounds

We're not aware of any workaround except for being careful whom to give script right, which is a general recommendation.

References

@michitux michitux published to xwiki/xwiki-platform Apr 29, 2025
Published to the GitHub Advisory Database Apr 29, 2025
Reviewed Apr 29, 2025
Published by the National Vulnerability Database Apr 30, 2025
Last updated Apr 30, 2025

Severity

Low

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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

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

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.
(13th percentile)

Weaknesses

CVE ID

CVE-2025-32972

GHSA ID

GHSA-rp38-24m3-rx87

Source code

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