CVE-2024-26138: License information is public, exposing instance id and license holder details

Published Feb 21, 2024
·
Updated

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 https://github.com/xwikisas/application-licensing/commit/d168fb88fc0d121bf95e769ea21c55c00bebe5a6

Workarounds There are no known workarounds besides upgrading.

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

Other sources

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.

NVD

Affected Software

2 affected componentsFixes available
maven/com.xwiki.licensing:application-licensing-licensor-ui>=1.0<1.24.2
1.24.2
XWiki Application Licensing Xwiki>=1.0<1.24.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/com.xwiki.licensing:application-licensing-licensor-ui to a version that resolves this vulnerability.

    Fixed in 1.24.2
  2. Upgrade

    Upgrade application-licensing (XWiki licensor application) to a version that resolves this vulnerability.

    Fixed in 1.24.2Patch d168fb88fc0d121bf95e769ea21c55c00bebe5a6

Event History

Feb 21, 2024
CVE Published
via MITRE·04:52 PM
Data Sourced
via MITRE·04:52 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
RemedyAffected Software
Advisory Published
via GitHub·06:04 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-26138?

CVE-2024-26138 is classified as a high-severity vulnerability due to the exposure of sensitive instance information.

2

What software versions are affected by CVE-2024-26138?

CVE-2024-26138 affects XWiki application licensing versions between 1.0 and 1.24.2.

3

How do I fix CVE-2024-26138?

To fix CVE-2024-26138, upgrade to the latest version of the affected software that resolves the exposure issue.

4

What information is exposed by CVE-2024-26138?

CVE-2024-26138 exposes sensitive license details, including instance identifiers and license status, to the public.

5

Is there a workaround for CVE-2024-26138?

There is no documented workaround for CVE-2024-26138, and upgrading to a fixed version is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203