How severe is CVE-2025-54125?

No CVSS score has been assigned to CVE-2025-54125 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-54125?

CVE-2025-54125 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 CVE-2025-54125?

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 CVE-2025-54125 is resolved across your whole dependency graph.

How do I detect CVE-2025-54125 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 CVE-2025-54125 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 CVE-2025-54125 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-54125 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 CVE-2025-54125?

CVE-2025-54125 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th 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 CVE-2025-54125?

CVE-2025-54125 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.

Is there exploit tooling available for CVE-2025-54125?

A Nuclei detection template exists for CVE-2025-54125, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2025-54125 published, and has it been updated?

CVE-2025-54125 was published on August 5, 2025 and was last updated on October 28, 2026. 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

CVE-2025-54125 — xwiki-platform-oldcore

Fix: xwiki/xwiki-platform@742ee34

CVE-2025-54125 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.

XWiki Platform: Password and email exposure in xml.vm fields

Also known asGHSA-57q2-6cp4-9mq3

Published

Aug 5, 2025

Updated

Oct 28, 2026

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.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-54125.

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs74th percentile — riskier than 74% 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

The XML export of a page in XWiki that can be triggered by any user with view rights on a page by appending ?xpage=xml to the URL includes password and email properties stored on a document that aren't named password or email. This allows any user to obtain the salted and hashed user account validation or password reset token. As those tokens are randomly generated strings, the immediate impact of this should be low. The user's password and email itself aren't exposed as those fields are named password and email and thus aren't affected. However, depending on how the wiki is used, there could be extensions or custom code that store passwords in plain text in such password properties that would be exposed by this vulnerability.

Patches

This vulnerability has been fixed by completely removing the output of password and email fields in this XML export in versions 17.2.0 RC1, 16.10.5 and 16.4.7.

Workarounds

If this XML export isn't needed, the file templates/xml.vm in the deployed WAR can be deleted. There isn't any feature in XWiki itself that depends on this XML export.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-oldcore`	≥ 1.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`	≥ 1.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 CVE-2025-54125 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.

How to detect CVE-2025-54125

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2025-54125 -u https://target

Template: XWiki XML View - Sensitive Information Exposure
Severity: high
Impact: Unauthenticated attackers can access sensitive information including passwords and email addresses stored in custom user profile fields through the XML view functionality.
Remediation: Upgrade XWiki to the latest version that properly protects sensitive custom fields in XML view outputs.

Template by ProjectDiscovery nuclei-templates (ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Impact The XML export of a page in XWiki that can be triggered by any user with view rights on a page by appending `?xpage=xml` to the URL includes password and email properties stored on a document that aren't named `password` or `email`. This allows any user to obtain the salted and hashed user account validation or password reset token. As those tokens are randomly generated strings, the immediate impact of this should be low. The user's password and email itself aren't exposed as those fields are named `password` and `email` and thus aren't affected. However, depending on how the wiki

O3 Security · Impact-Aware SCA

Is CVE-2025-54125 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works