XWiki extension license information is public, exposing instance id and license holder details
CVE-2024-26138GHSA-4hfp-m9gv-m753
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (com.xwiki.licensing:application-licensing-licensor-ui 1.24.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven com.xwiki.licensing:application-licensing-licensor-ui
- Affected
- >= 1.0, < 1.24.2
- Fixed in
- 1.24.2
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-4hfp-m9gv-m753 lists affected ranges: Maven com.xwiki.licensing:application-licensing-licensor-ui >=1.0 <1.24.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2024-26138: 0.49% estimated exploitation activity in the next 30 days; percentile 42.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact The licensor application 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). Patches This has been fixed in Application Licensing 1.24.2, by…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-4hfp-m9gv-m753
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-26138 Advisory: XWiki extension license information is public, exposing instance id and license holder details IDs: CVE-2024-26138, GHSA-4hfp-m9gv-m753 Record: https://patchnext.com/advisories/cve-2024-26138 (revision 1, source checked 26 Oct 2026, 16:44 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: com.xwiki.licensing:application-licensing-licensor-ui 1.24.2. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven com.xwiki.licensing:application-licensing-licensor-ui: affected >= 1.0, < 1.24.2; fixed in 1.24.2 ## Suggested inspection (read-only) - Maven com.xwiki.licensing:application-licensing-licensor-ui: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on com.xwiki.licensing:application-licensing-licensor-ui. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-4hfp-m9gv-m753 (GitHub-reviewed advisory GHSA-4hfp-m9gv-m753 lists affected ranges: Maven com.xwiki.licensing:application-licensing-licensor-ui >=1.0 <1.24.2) Commands are suggestions: review each one before running it.
Loading voting…