CVE-2025-58049

Workarounds

We're not aware of any workarounds except for upgrading.

The PDF export uses a background job that runs on the server-side. Jobs like this have a status that is serialized in the permanent directory when the job is finished. The job status includes the job request. The PDF export job request is initialized, before the job starts, with some context information that is needed to replicate the HTTP request (used to trigger the export) in the background thread used to run the export job. This context information includes the cookies from the HTTP request that triggered the export. As a result, the user cookies (including the encrypted username and password) are stored in the permanent directory after the PDF export is finished. As the encryption key is stored in the same data directory (by default it is generated in data/configuration.properties), this means that this job status contains the equivalent of the plain text password of the user who requested the PDF export.

XWiki shouldn't store passwords in plain text, and it shouldn't be possible to gain access to plain text passwords by gaining access to, e.g., a backup of the data directory.

CVE-2025-58049 has a CVSS score of 5.8 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (16.4.8, 16.10.7, 17.4.0-rc-1); upgrading removes the vulnerable code path.

Kodem intelligence

This vulnerability has been patched in XWiki 16.4.8, 16.10.7 and 17.4.0RC1.

1. What is CVE-2025-58049? CVE-2025-58049 is a medium-severity security vulnerability in org.xwiki.platform:xwiki-platform-export-pdf-api (maven), affecting versions >= 14.4.2, < 16.4.8. It is fixed in 16.4.8, 16.10.7, 17.4.0-rc-1.
2. How severe is CVE-2025-58049? CVE-2025-58049 has a CVSS score of 5.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.xwiki.platform:xwiki-platform-export-pdf-api are affected by CVE-2025-58049? org.xwiki.platform:xwiki-platform-export-pdf-api (maven) versions >= 14.4.2, < 16.4.8 is affected.
4. Is there a fix for CVE-2025-58049? Yes. CVE-2025-58049 is fixed in 16.4.8, 16.10.7, 17.4.0-rc-1. Upgrade to this version or later.
5. Is CVE-2025-58049 exploitable, and should I be worried? Whether CVE-2025-58049 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-58049 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-58049?
   • Upgrade org.xwiki.platform:xwiki-platform-export-pdf-api to 16.4.8 or later
   • Upgrade org.xwiki.platform:xwiki-platform-export-pdf-api to 16.10.7 or later
   • Upgrade org.xwiki.platform:xwiki-platform-export-pdf-api to 17.4.0-rc-1 or later