CVE-2025-54125: XWiki Platform: Password and email exposure in xml.vm fields

Published Aug 5, 2025
·
Updated

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.

Other sources

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. XWiki Platform Legacy Old Core and XWiki Platform Old Core versions 1.1 through 16.4.6, 16.5.0-rc-1 through 16.10.4 and 17.0.0-rc-1 through 17.1.0, 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 is fixed in versions 16.4.7, 16.10.5 and 17.2.0-rc-1. To work around this issue, the file templates/xml.vm in the deployed WAR can be deleted if the XML isn't needed. There isn't any feature in XWiki itself that depends on the XML export.

— MITRE

Affected Software

9 affected componentsFixes available
maven/org.xwiki.platform:xwiki-platform-legacy-oldcore>=17.0.0-rc-1<17.2.0-rc-1
17.2.0-rc-1
maven/org.xwiki.platform:xwiki-platform-legacy-oldcore>=16.5.0-rc-1<16.10.5
16.10.5
maven/org.xwiki.platform:xwiki-platform-legacy-oldcore>=1.1<16.4.7
16.4.7
maven/org.xwiki.platform:xwiki-platform-oldcore>=17.0.0-rc-1<17.2.0-rc-1
17.2.0-rc-1
maven/org.xwiki.platform:xwiki-platform-oldcore>=16.5.0-rc-1<16.10.5
16.10.5
maven/org.xwiki.platform:xwiki-platform-oldcore>=1.1<16.4.7
16.4.7
XWiki xwiki>=1.1<16.4.7
XWiki xwiki>=16.5.0<16.10.5
XWiki xwiki>=17.0.0<=17.1.0

Event History

Aug 5, 2025
Advisory Published
via GitHub·05:13 PM
Data Sourced
via GitHub·05:13 PM
DescriptionWeaknessAffected Software
CVE Published
via MITRE·11:30 PM
Data Sourced
via MITRE·11:30 PM
DescriptionWeakness
Aug 6, 2025
Data Sourced
via NVD·12:15 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:15 AM
RemedyAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-54125?

CVE-2025-54125 has been rated as a high severity vulnerability due to the potential exposure of sensitive information.

2

How do I fix CVE-2025-54125?

To fix CVE-2025-54125, upgrade to the following versions: 17.2.0-rc-1, 16.10.5, or 16.4.7.

3

What types of data are exposed in CVE-2025-54125?

CVE-2025-54125 exposes password and email properties that may not be explicitly named 'password' or 'email'.

4

Who is affected by CVE-2025-54125?

Any user with view rights on a page in XWiki is affected by CVE-2025-54125.

5

What software versions are vulnerable to CVE-2025-54125?

Versions of XWiki prior to 17.2.0-rc-1, 16.10.5, and 16.4.7 are vulnerable to CVE-2025-54125.

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