License information is public, exposing instance id and license holder details

CVE Details

Basic Information

Title License information is public, exposing instance id and license holder details
Type cve
Published 2024-02-21T16:52:25.022Z
Modified 2025-04-22T16:23:41.846Z

Product Information

Vendor xwikisas
Product application-licensing
Version >= 1.0, < 1.24.2

CVSS Information

Base Score 5.3 (MEDIUM)
Attack Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

AI Analysis

AI Description The XWiki licensor application exposes sensitive license information, including instance IDs and user details, which could be used for phishing attacks. This information was mistakenly made public and has been fixed in version 1.24.2.
AI Severity Medium
AI Vendor XWiki SAS
AI Product Application Licensing
AI Version 1.0, 1.24.2

Affected Products

  • xwikisas application-licensing >= 1.0, < 1.24.2

Additional Information

CWE List CWE-862
Source GitHub_M

Description

The XWiki licensor application, which manages and enforce application licenses for paid extensions, includes the document `Licenses.Code.LicenseJSON` that provides information for admins regarding active licenses. This document is public and thus exposes this information publicly. The information includes the instance’s id as well as first and last name and email of the license owner. This is a leak of information that isn’t supposed to be public. The instance id allows associating data on the active installs data with the concrete XWiki instance. Active installs assures that “there’s no way to find who’s having a given UUID” (referring to the instance id). Further, the information who the license owner is and information about the obtained licenses can be used for targeted phishing attacks. Also, while user information is normally public, email addresses might only be displayed obfuscated, depending on the configuration. This has been fixed in Application Licensing 1.24.2. There are no known workarounds besides upgrading.

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.