CVE-2025-32970

Workarounds

A web application firewall could be configured to reject requests with the xerror parameter as from our analysis this parameter isn't used anymore. For requests with the RequiresHTMLConversion parameter set, the referrer URL should be checked if it points to the XWiki installation. Apart from that, we're not aware of any workarounds.

An open redirect vulnerability in the HTML conversion request filter allows attackers to construct URLs on an XWiki instance that redirect to any URL. To reproduce, open <xwiki-host>/xwiki/bin/view/Main/?foo=bar&foo_syntax=invalid&RequiresHTMLConversion=foo&xerror=https://www.example.com/ where <xwiki-host> is the URL of your XWiki installation.

Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites. Typical impact: phishing and credential harvesting via a trusted domain.

CVE-2025-32970 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. 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 (15.10.13, 16.4.4, 16.8.0); upgrading removes the vulnerable code path.

Kodem intelligence

This bug has been fixed in XWiki 15.10.13, 16.4.4 and 16.8.0 by validating the domain of the redirect URL against the configured safe domains and the current request's domain.

1. What is CVE-2025-32970? CVE-2025-32970 is a medium-severity open redirect vulnerability in org.xwiki.platform:xwiki-platform-wysiwyg-api (maven), affecting versions >= 13.5-rc-1, < 15.10.13. It is fixed in 15.10.13, 16.4.4, 16.8.0. Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites.
2. How severe is CVE-2025-32970? CVE-2025-32970 has a CVSS score of 6.1 (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-wysiwyg-api are affected by CVE-2025-32970? org.xwiki.platform:xwiki-platform-wysiwyg-api (maven) versions >= 13.5-rc-1, < 15.10.13 is affected.
4. Is there a fix for CVE-2025-32970? Yes. CVE-2025-32970 is fixed in 15.10.13, 16.4.4, 16.8.0. Upgrade to this version or later.
5. Is CVE-2025-32970 exploitable, and should I be worried? Whether CVE-2025-32970 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-32970 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-32970?
   • Upgrade org.xwiki.platform:xwiki-platform-wysiwyg-api to 15.10.13 or later
   • Upgrade org.xwiki.platform:xwiki-platform-wysiwyg-api to 16.4.4 or later
   • Upgrade org.xwiki.platform:xwiki-platform-wysiwyg-api to 16.8.0 or later