xwiki-platform up to 16.7.1 exposure of resource

Summaryinfo

A vulnerability marked as problematic has been reported in xwiki-platform up to 16.7.1. The impacted element is an unknown function. This manipulation causes exposure of resource. This vulnerability appears as CVE-2025-32783. The attack may be initiated remotely. There is no available exploit. It is advised to disable the affected component.

Detailsinfo

A vulnerability was found in xwiki-platform up to 16.7.1. It has been declared as problematic. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a exposure of resource vulnerability. The CWE definition for the vulnerability is CWE-668. The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. As an impact it is known to affect confidentiality. The summary by CVE is:

XWiki Platform is a generic wiki platform. A vulnerability in versions from 5.0 to 16.7.1 affects users with Message Stream enabled and a wiki configured as closed from selecting "Prevent unregistered users to view pages" in the Administrations Rights. The vulnerability is that any message sent in a subwiki to "everyone" is actually sent to the farm: any visitor of the main wiki will be able to see that message through the Dashboard, even if the subwiki is configured to be private. This issue will not be patched as Message Stream has been deprecated in XWiki 16.8.0RC1 and is not maintained anymore. A workaround for this issue involves keeping Message Stream disabled by default. It's advised to keep it disabled from Administration > Social > Message Stream.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2025-32783 since 04/10/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.

The best possible mitigation is suggested to be disabling the affected component.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Content Management System

Name

• xwiki-platform

Version

• 16.7.0
• 16.7.1

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion