Skip to content

← Actionable
High, CVSS 7.1

XWiki leaks password hashes and other accessible password properties

CVE-2025-54124GHSA-r38m-cgpg-qj69

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.xwiki.platform:xwiki-platform-oldcore 17.2.0-rc-1, 16.10.5, 16.4.7; org.xwiki.platform:xwiki-platform-legacy-oldcore 17.2.0-rc-1, 16.10.5, 16.4.7), 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

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-r38m-cgpg-qj69 lists affected ranges: Maven org.xwiki.platform:xwiki-platform-oldcore >=9.8-rc-1 =16.5.0-rc-1 =17.0.0-rc-1 =9.8-rc-1 =16.5.0-rc-1 =17.0.0-rc-1 <17.2.0-rc-1

    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 4.0
7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2025-54124: 0.48% estimated exploitation activity in the next 30 days; percentile 41.50 (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 Any user with edit right on a page of the wiki can create an XClass with a database list property that references a password property, for example the password hash that is stored for users. When adding an object of that XClass, the content of that password property is displayed. In practice, with a standard rights setup, this means that any user with an account on the wiki can access password hashes of all users, and possibly other password properties (with hashed or plain storage) that are on pages that the user can view. Patches This vulnerability has been pached in XWiki 16.4.7, 16.10.5, and 17.2.0 by disallowing the use of password properties in database list properties. Additionally, queries for email properties are disallowed, too, when email obfuscation is enabled. Workarounds We're not aware of any workarounds.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-r38m-cgpg-qj69

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-2025-54124

Advisory: XWiki leaks password hashes and other accessible password properties
IDs: CVE-2025-54124, GHSA-r38m-cgpg-qj69
Record: https://patchnext.com/advisories/cve-2025-54124 (revision 1, source checked 26 Oct 2026, 16:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.xwiki.platform:xwiki-platform-oldcore 17.2.0-rc-1, 16.10.5, 16.4.7; org.xwiki.platform:xwiki-platform-legacy-oldcore 17.2.0-rc-1, 16.10.5, 16.4.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.xwiki.platform:xwiki-platform-oldcore: affected >= 9.8-rc-1, < 16.4.7; >= 16.5.0-rc-1, < 16.10.5; >= 17.0.0-rc-1, < 17.2.0-rc-1; fixed in 17.2.0-rc-1, 16.10.5, 16.4.7
- Maven org.xwiki.platform:xwiki-platform-legacy-oldcore: affected >= 9.8-rc-1, < 16.4.7; >= 16.5.0-rc-1, < 16.10.5; >= 17.0.0-rc-1, < 17.2.0-rc-1; fixed in 17.2.0-rc-1, 16.10.5, 16.4.7

## Suggested inspection (read-only)
- Maven org.xwiki.platform:xwiki-platform-oldcore: check the installed version with your package manager.
- Maven org.xwiki.platform:xwiki-platform-legacy-oldcore: 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 org.xwiki.platform:xwiki-platform-oldcore, org.xwiki.platform:xwiki-platform-legacy-oldcore.
- 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-r38m-cgpg-qj69 (GitHub-reviewed advisory GHSA-r38m-cgpg-qj69 lists affected ranges: Maven org.xwiki.platform:xwiki-platform-oldcore >=9.8-rc-1 =16.5.0-rc-1 =17.0.0-rc-1 =9.8-rc-1 =16.5.0-rc-1 =17.0.0-rc-1 <17.2.0-rc-1)

Commands are suggestions: review each one before running it.

Loading voting…