CVE-2025-55749 — xwiki-platform-tool-jetty…
Fix: xwiki/xwiki-platform@42fb063CVE-2025-55749 is a CWE-284 vulnerability in org.xwiki.platform:xwiki-platform-tool-jetty-resources. A fix is available for org.xwiki.platform:xwiki-platform-tool-jetty-resources — see the affected versions and patch details below.
The XWiki Jetty package (XJetty) allows accessing any application file through URL
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-55749.
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-tool-jetty-resources☕org.xwiki.platform:xwiki-platform-tool-jetty-resources☕org.xwiki.platform:xwiki-platform-tool-jetty-resourcesReal-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
In an instance which is using the XWiki Jetty package (XJetty), a context is exposed to statically access any file located in the webapp/ folder.
It allows accessing files which might contains credentials, like http://myhots/webapps/xwiki/WEB-INF/xwiki.cfg, http://myhots/webapps/xwiki/WEB-INF/xwiki.properties or http://myhots/webapps/xwiki/WEB-INF/hibernate.cfg.xml.
Patches
This has been patched in 16.10.11, 17.4.4, 17.7.0.
Workarounds
The workaround is to modify the start_xwiki.sh script following https://github.com/xwiki/xwiki-platform/compare/8b68d8a70b43f25391b3ee48477d7eb71b95cf4b...99a04a0e2143583f5154a43e02174155da7e8e10.
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
Attribution
Vulnerability reported by Joseph Huber.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-tool-jetty-resources | ≥ 16.7.0&&< 16.10.11 | 16.10.11org.xwiki.platform:xwiki-platform-tool-jetty-resources:16.10.11 |
| ☕Maven | org.xwiki.platform:xwiki-platform-tool-jetty-resources | ≥ 17.0.0-rc-1&&< 17.4.4 | 17.4.4org.xwiki.platform:xwiki-platform-tool-jetty-resources:17.4.4 |
| ☕Maven | org.xwiki.platform:xwiki-platform-tool-jetty-resources | ≥ 17.5.0&&< 17.7.0 | 17.7.0org.xwiki.platform:xwiki-platform-tool-jetty-resources:17.7.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-tool-jetty-resources, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-tool-jetty-resources to 16.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-55749 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-55749 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-55749. 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-55749
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2025-55749 -u https://target- Template
- XWiki - Information Disclosure
- Severity
- high
- Impact
- Attackers can access sensitive files including credentials, leading to information disclosure.
- Remediation
- Update to versions 16.10.11, 17.4.4, or 17.7.0 or later.
Template by ProjectDiscovery nuclei-templates (DhiyaneshDk), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2025-55749 in your dependencies?
O3 Security finds CVE-2025-55749 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.