Skip to content

GHSA-ghf6-2f42-mjh9 CVE-2023-45135

XWiki users can be tricked to execute scripts as the create page action doesn't display the page's title

High Maven
Severity
9.0 / 10
High · CVSS 3.1
Exploit chance (EPSS)
1.91%
Chance of exploitation in the next 30 days. Higher than 79.82% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-116 Improper Encoding or Escaping of Output
Fix
Available
2 packages have a fixed version

Description

Impact

In XWiki, it is possible to pass a title to the page creation action that isn't displayed at first but then executed in the second step. This can be used by an attacker to trick a victim to execute code, allowing script execution if the victim has script right or remote code execution including full access to the XWiki instance if the victim has programming right.

For the attack to work, the attacker needs to convince the victim to visit a link like <xwiki-host>/xwiki/bin/create/NonExistingSpace/WebHome?title=$services.logging.getLogger(%22foo%22).error(%22Script%20executed!%22) where <xwiki-host> is the URL of the Wiki installation and to then click on the "Create" button on that page. The page looks like a regular XWiki page that the victim would also see when clicking the button to create a page that doesn't exist yet, the malicious code is not displayed anywhere on that page. After clicking the "Create" button, the malicious title would be displayed but at this point, the code has already been executed and the attacker could use this code also to hide the attack, e.g., by redirecting the victim again to the same page with an innocent title. It thus seems plausible that this attack could work if the attacker can place a fake "create page" button on a page which is possible with edit right.

Patches

This has been patched in XWiki 14.10.2 and 15.5RC1 by displaying the title already in the first step such that the victim can notice the attack before continuing.

Workarounds

It is possible to manually patch the modified files from the patch in an existing installation. For the JavaScript change, the minified JavaScript file would need to be obtained from a build of XWiki and replaced accordingly.

Affected versions

Maven

PackageVulnerableFixed in
org.xwiki.platform:xwiki-platform-web
>= 7.2-milestone-2, < 14.10.12
14.10.12
org.xwiki.platform:xwiki-platform-web-templates
< 14.10.12
14.10.12
org.xwiki.platform:xwiki-platform-web-templates
>= 15.0-rc-1, < 15.5-rc-1
15.5-rc-1

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-web Maven → 14.10.12

maven
<dependency><groupId>org.xwiki.platform</groupId><artifactId>xwiki-platform-web</artifactId><version>14.10.12</version></dependency>
gradle
implementation("org.xwiki.platform:xwiki-platform-web:14.10.12")

org.xwiki.platform:xwiki-platform-web-templates Maven → 14.10.12

maven
<dependency><groupId>org.xwiki.platform</groupId><artifactId>xwiki-platform-web-templates</artifactId><version>14.10.12</version></dependency>
gradle
implementation("org.xwiki.platform:xwiki-platform-web-templates:14.10.12")

Severity breakdown

CVSS 3.1 9.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-116: Improper Encoding or Escaping of Output

The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.

How to prevent it
  • Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using the ESAPI Encoding control [REF-45] or a similar tool, library, or framework. These will help the programmer encode outputs in a manner less prone to error. Alternately, use built-in functions, but consider using wrappers in case those functions are discovered to have a vulnerability.
  • Architecture and Design: If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated. For example, stored procedures can enforce database query structure and reduce the likelihood of SQL injection.
  • Architecture and Design, Implementation: Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies.
  • Architecture and Design: In some cases, input validation may be an important strategy when output encoding is not a complete solution. For example, you may be providing the same output that will be processed by multiple consumers that use different encodings or representations. In other cases, you may be required to allow user-supplied input to contain control information, such as limited HTML tags that support formatting in a wiki or bulletin board. When this type of requirement must be met, use an extremely strict allowlist to limit which control sequences can be used. Verify that the resulting syntactic structure is what you expect. Use your normal encoding methods for the remainder of the input.
  • Architecture and Design: Use input validation as a defense-in-depth measure to reduce the likelihood of output encoding errors (see CWE-20).
  • Requirements: Fully specify which encodings are required by components that will be communicating with each other.
  • Implementation: When exchanging data between components, ensure that both components are using the same character encoding. Ensure that the proper encoding is applied at each interface. Explicitly set the encoding you are using whenever the protocol allows you to do so.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-w4fj-87j5-f25c
XWiki has Reflected Cross-Site Scripting (XSS) in page history compare
Medium Also affects org.xwiki.platform:xwiki-platform-web-templates
GHSA-wvqx-m5px-6cmp
XWiki Affected by Reflected Cross-Site Scripting (XSS) in Error Messages
Medium Also affects org.xwiki.platform:xwiki-platform-web-templates
GHSA-7vpr-jm38-wr7w
XWiki vulnerable to a reflected XSS via xredirect parameter in DeleteApplication
Medium Also affects org.xwiki.platform:xwiki-platform-web-templates
GHSA-m9x4-w7p9-mxhx
XWiki allows Reflected XSS in two templates
Medium Also affects org.xwiki.platform:xwiki-platform-web-templates
GHSA-f963-4cq8-2gw7
In XWiki Platform, payloads stored in content is executed when a user with script/programming right edit them
High Also affects org.xwiki.platform:xwiki-platform-web-templates
GHSA-692v-783f-mg8x
XWiki Platform vulnerable to Cross-Site Scripting (XSS) through conflict resolution
Medium Also affects org.xwiki.platform:xwiki-platform-web-templates
GHSA-93gh-jgjj-r929
XWiki Platform vulnerable to XSS with edit right in the create document form for existing pages
Medium Also affects org.xwiki.platform:xwiki-platform-web
GHSA-qcj9-gcpg-4w2w
XWiki Platform web templates vulnerable to reflected XSS in the create document form if name validation is enabled
Critical Also affects org.xwiki.platform:xwiki-platform-web-templates
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