CVE-2025-49580 — xwiki-platform-refactorin…
Fix: xwiki/xwiki-platform@ab209acCVE-2025-49580 is a CWE-266 vulnerability in org.xwiki.platform:xwiki-platform-refactoring-default. A fix is available for org.xwiki.platform:xwiki-platform-refactoring-default — see the affected versions and patch details below.
XWiki allows privilege escalation through link refactoring
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.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-49580.
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.
Real-World Exposure
org.xwiki.platform:xwiki-platform-refactoring-default☕org.xwiki.platform:xwiki-platform-refactoring-default☕org.xwiki.platform:xwiki-platform-refactoring-default☕org.xwiki.platform:xwiki-platform-refactoring-defaultReal-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
Pages can gain script or programming rights when they contain a link and the target of the link is renamed or moved. This might lead to execution of scripts contained in xobjects that should have never been executed. This vulnerability affects all version of XWiki since 8.2 and 7.4.5.
Patches
The patch consists in only setting the originalMetadataAuthor when performing such change, so that it's displayed in the history but it has no impact on the right evaluation (i.e. the original author of the changes is still used for right computation).
This patch has been applied on XWiki 16.4.7, 17.1.0RC1, 16.10.4.
Workarounds
There's no workaround for this vulnerability, except preventing to perform any refactoring operation with users having more than edit rights.
Administrators are strongly advised to upgrade. If not possible, the patch only impacts module xwiki-platform-refactoring-default so it's possible to apply the commit and rebuild and deploy only that module.
CVSS explanation
Attack vector: Network - Always for XWiki. Complexity: Low - The set of operations to perform the attack is quite easy. Attack requirements: None - Any system is vulnerable, it doesn't depend on specific condition other than user interaction. Privileges required: Low - The attacker only needs edit rights. User interaction: Active - To be successful the attack needs someone with more rights to perform a move/rename of a specific page. Confidentiality: High - The attack might lead to execution of any script. Integrity: High - The attack might lead to execution of any script. Availability: High - The attack might lead to execution of any script. Subsequent system impacts: None for any criteria. Only current system is affected.
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira XWiki.org
- Email us at Security Mailing List
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-refactoring-default | ≥ 17.0.0-rc-1&&< 17.1.0-rc-1 | 17.1.0-rc-1org.xwiki.platform:xwiki-platform-refactoring-default:17.1.0-rc-1 |
| ☕Maven | org.xwiki.platform:xwiki-platform-refactoring-default | ≥ 16.5.0-rc-1&&< 16.10.4 | 16.10.4org.xwiki.platform:xwiki-platform-refactoring-default:16.10.4 |
| ☕Maven | org.xwiki.platform:xwiki-platform-refactoring-default | ≥ 8.2&&< 16.4.7 | 16.4.7org.xwiki.platform:xwiki-platform-refactoring-default:16.4.7 |
| ☕Maven | org.xwiki.platform:xwiki-platform-refactoring-default | ≥ 7.4.5&&< 16.4.7 | 16.4.7org.xwiki.platform:xwiki-platform-refactoring-default:16.4.7 |
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-refactoring-default, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-refactoring-default to 17.1.0-rc-1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-49580 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-49580 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-49580. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-49580 in your dependencies?
O3 Security finds CVE-2025-49580 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.