How severe is GHSA-r38m-cgpg-qj69?

No CVSS score has been assigned to GHSA-r38m-cgpg-qj69 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r38m-cgpg-qj69?

GHSA-r38m-cgpg-qj69 affects the following packages: org.xwiki.platform:xwiki-platform-oldcore (Maven), org.xwiki.platform:xwiki-platform-oldcore (Maven), org.xwiki.platform:xwiki-platform-oldcore (Maven), org.xwiki.platform:xwiki-platform-legacy-oldcore (Maven), org.xwiki.platform:xwiki-platform-legacy-oldcore (Maven), org.xwiki.platform:xwiki-platform-legacy-oldcore (Maven). Ecosystems affected: Maven.

How do I fix GHSA-r38m-cgpg-qj69?

Update org.xwiki.platform:xwiki-platform-oldcore to 16.4.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r38m-cgpg-qj69 is resolved across your whole dependency graph.

How do I detect GHSA-r38m-cgpg-qj69 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-oldcore, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-r38m-cgpg-qj69 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-r38m-cgpg-qj69 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r38m-cgpg-qj69 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-r38m-cgpg-qj69?

GHSA-r38m-cgpg-qj69 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-r38m-cgpg-qj69?

GHSA-r38m-cgpg-qj69 is classified as CWE-359 (CWE-359). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r38m-cgpg-qj69 published, and has it been updated?

GHSA-r38m-cgpg-qj69 was published on August 5, 2025 and was last updated on August 6, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

XWiki leaks password hashes and other accessible password propertiesGHSA-r38m-cgpg-qj69

Fix: xwiki/xwiki-platform@f2ca864

GHSA-r38m-cgpg-qj69 is a CWE-359 vulnerability in org.xwiki.platform:xwiki-platform-oldcore. A fix is available for org.xwiki.platform:xwiki-platform-oldcore — see the affected versions and patch details below.

Also known asCVE-2025-54124

Published

Aug 5, 2025

Updated

Aug 6, 2025

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-r38m-cgpg-qj69.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

6 pkgs affected

☕org.xwiki.platform:xwiki-platform-oldcore☕org.xwiki.platform:xwiki-platform-oldcore☕org.xwiki.platform:xwiki-platform-oldcore☕org.xwiki.platform:xwiki-platform-legacy-oldcore☕org.xwiki.platform:xwiki-platform-legacy-oldcore☕org.xwiki.platform:xwiki-platform-legacy-oldcore

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-oldcore`	≥ 9.8-rc-1&&< 16.4.7	16.4.7`org.xwiki.platform:xwiki-platform-oldcore:16.4.7`
☕Maven	`org.xwiki.platform:xwiki-platform-oldcore`	≥ 16.5.0-rc-1&&< 16.10.5	16.10.5`org.xwiki.platform:xwiki-platform-oldcore:16.10.5`
☕Maven	`org.xwiki.platform:xwiki-platform-oldcore`	≥ 17.0.0-rc-1&&< 17.2.0-rc-1	17.2.0-rc-1`org.xwiki.platform:xwiki-platform-oldcore:17.2.0-rc-1`
☕Maven	`org.xwiki.platform:xwiki-platform-legacy-oldcore`	≥ 9.8-rc-1&&< 16.4.7	16.4.7`org.xwiki.platform:xwiki-platform-legacy-oldcore:16.4.7`
☕Maven	`org.xwiki.platform:xwiki-platform-legacy-oldcore`	≥ 16.5.0-rc-1&&< 16.10.5	16.10.5`org.xwiki.platform:xwiki-platform-legacy-oldcore:16.10.5`
☕Maven	`org.xwiki.platform:xwiki-platform-legacy-oldcore`	≥ 17.0.0-rc-1&&< 17.2.0-rc-1	17.2.0-rc-1`org.xwiki.platform:xwiki-platform-legacy-oldcore:17.2.0-rc-1`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 17.0.0 && ≤ 17.1.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-oldcore, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-oldcore to 16.4.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r38m-cgpg-qj69 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-r38m-cgpg-qj69 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works