GHSA-qj4x-9g63-25g6 CVE-2026-34151

XWiki Platform Old Core: Resource path traversal via /skin/ action endpoint in Jetty 12+

High Maven

Severity: 0.0 / 10; High · CVSS 4.0
Exploit chance (EPSS): 2.47%; Chance of exploitation in the next 30 days. Higher than 84.51% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-24 Path Traversal: '../filedir'
Fix: 17.10.5; Upgrade org.xwiki.platform:xwiki-platform-oldcore to this version or later

Description

Impact

With Jetty 12+ a user can craft a URL to access any resource the Jetty instance is allowed to access.

For example http://[host]/xwiki/bin/skin/..%252f/..%252f..%252f..%252f..%252f..%252f..%252f..%252fetc/passwd allows downloading the content of the /etc/passwd file, provided Jetty is allowed to read it, and if your XWiki webapp is located exactly 5 levels below / (like /var/lib/jetty/webapps/xwiki, which is the case in the docker image, for example).

Another example which does not go out of the XWiki webapp, but it's still a vulnerability (since users should not be allowed to access Hibernate or XWiki configuration files) is http://[host]/xwiki/bin/skin/..%252f/..%252fWEB-INF/xwiki.cfg.

Patches

This vulnerability has been patched in XWiki 17.10.5 and 18.2.0.

Workarounds

A possible workaround is to use a different application server, like Jetty < 12 (in the case of XWiki < 17) or Tomcat, which don't seem to be impacted.

Resources

For more information

If there are any questions or comments about this advisory:

Open an issue in Jira XWiki.org
Send an email to the Security Mailing List

Attribution

Lê Ngọc Khoa reported the vulnerability.

Affected versions

Maven

Package	Vulnerable	Fixed in
org.xwiki.platform:xwiki-platform-oldcore	`< 17.10.5`	`17.10.5`
org.xwiki.platform:xwiki-platform-oldcore	`>= 18.0.0-rc-1, < 18.2.0`	`18.2.0`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.xwiki.platform:xwiki-platform-oldcore Maven → `17.10.5`

maven

<dependency><groupId>org.xwiki.platform</groupId><artifactId>xwiki-platform-oldcore</artifactId><version>17.10.5</version></dependency>

gradle

implementation("org.xwiki.platform:xwiki-platform-oldcore:17.10.5")

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack vector: Network
Attack complexity: Low
Attack requirements: Present
Privileges required: None
User interaction: None
Confidentiality (vulnerable system): High
Integrity (vulnerable system): None
Availability (vulnerable system): None
Confidentiality (subsequent systems): None
Integrity (subsequent systems): None
Availability (subsequent systems): None

Weakness

CWE-24: Path Traversal: '../filedir'

The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "../" sequences that can resolve to a location that is outside of that directory.

How to prevent it

Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434. Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would b
Implementation: Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.

References

Packages

github.com/xwiki/xwiki-platform

Timeline

Jul 7, 2026 Published
Sep 30, 2026 Last updated by the source
Nov 1, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-mrqg-xmgm-rc5g XWiki's REST APIs can list all pages/spaces, leading to unavailability	High	Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-h259-74h5-4rh9 XWiki vulnerable to remote code execution with script right through unprotected Velocity scripting API	Critical	Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-57q2-6cp4-9mq3 XWiki exposes passwords and emails stored in fields not named password/email in xml.vm	Medium	Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-r38m-cgpg-qj69 XWiki leaks password hashes and other accessible password properties	Medium	Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-p9qm-p942-q3w5 XWiki Platform vulnerable to SQL injection through XWiki#searchDocuments API	Critical	Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-jp4x-w9cj-97q7 XWiki allows remote code execution through preview of XClass changes in AWM editor	High	Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-prwh-7838-xf82 XWiki allows SQL injection in query endpoint of REST API with Oracle	Critical	Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-g9jj-75mx-wjcx org.xwiki.platform:xwiki-platform-oldcore allows SQL injection in short form select requests through the script query API	High	Also affects org.xwiki.platform:xwiki-platform-oldcore

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor