CVE-2024-26138

XWiki extension license information is public, exposing instance id and license holder details

Workarounds

There are no known workarounds besides upgrading.

References

Fixed by https://github.com/xwikisas/application-licensing/commit/d168fb88fc0d121bf95e769ea21c55c00bebe5a6

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).

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2024-26138 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.24.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

This has been fixed in Application Licensing 1.24.2, by https://github.com/xwikisas/application-licensing/commit/d168fb88fc0d121bf95e769ea21c55c00bebe5a6

1. What is CVE-2024-26138? CVE-2024-26138 is a medium-severity missing authorization vulnerability in com.xwiki.licensing:application-licensing-licensor-ui (maven), affecting versions >= 1.0, < 1.24.2. It is fixed in 1.24.2. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2024-26138? CVE-2024-26138 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of com.xwiki.licensing:application-licensing-licensor-ui are affected by CVE-2024-26138? com.xwiki.licensing:application-licensing-licensor-ui (maven) versions >= 1.0, < 1.24.2 is affected.
4. Is there a fix for CVE-2024-26138? Yes. CVE-2024-26138 is fixed in 1.24.2. Upgrade to this version or later.
5. Is CVE-2024-26138 exploitable, and should I be worried? Whether CVE-2024-26138 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-26138 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-26138? Upgrade com.xwiki.licensing:application-licensing-licensor-ui to 1.24.2 or later.