CVE-2025-32970 is a medium-severity (CVSS 6.1) Open Redirect vulnerability in org.xwiki.platform:xwiki-platform-wysiwyg-api. A fix is available for org.xwiki.platform:xwiki-platform-wysiwyg-api — see the affected versions and patch details below.
org.xwiki.platform:xwiki-platform-wysiwyg-api Open Redirect vulnerability
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 CVE-2025-32970.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-32970 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.xwiki.platform:xwiki-platform-wysiwyg-api☕org.xwiki.platform:xwiki-platform-wysiwyg-api☕org.xwiki.platform:xwiki-platform-wysiwyg-apiReal-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
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.
Patches
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.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-wysiwyg-api | ≥ 13.5-rc-1&&< 15.10.13 | 15.10.13org.xwiki.platform:xwiki-platform-wysiwyg-api:15.10.13 |
| ☕Maven | org.xwiki.platform:xwiki-platform-wysiwyg-api | ≥ 16.0.0-rc-1&&< 16.4.4 | 16.4.4org.xwiki.platform:xwiki-platform-wysiwyg-api:16.4.4 |
| ☕Maven | org.xwiki.platform:xwiki-platform-wysiwyg-api | ≥ 16.5.0-rc-1&&< 16.8.0 | 16.8.0org.xwiki.platform:xwiki-platform-wysiwyg-api:16.8.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-wysiwyg-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-wysiwyg-api to 15.10.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32970 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 O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-32970 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-32970. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect CVE-2025-32970
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2025-32970 -u https://target- Template
- XWiki WYSIWYG API - Open Redirect
- Severity
- medium
- Impact
- Attackers can redirect users to malicious external websites through the xerror parameter, potentially enabling phishing attacks and credential theft.
- Remediation
- Upgrade to the latest XWiki version that properly validates redirect URLs in the WYSIWYG API.
Template by ProjectDiscovery nuclei-templates (ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2025-32970 in your dependencies?
O3 Security finds CVE-2025-32970 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.