Velocity execution without script right through tree macro

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

EPSS

• CVE-2023-50732: 0.49% estimated exploitation activity in the next 30 days; percentile 41.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact It's possible to execute a Velocity script without script right through the document tree. To reproduce: As a user without script right, create a document, e.g., named Nasty Title Set the document's title to $request.requestURI Click "Save & View" Reload the page in the browser The navigation panel displays a document named with the current URL, showing that the Velocity code has been executed even though the user doesn't have script right. Patches This has been patched in XWiki 14.10.7 and 15.2RC1. Workarounds A possible workaround is to: modify the page XWiki.DocumentTreeMacros search for the code #set ($discard = $translatedDocument.setTitle($translatedDocument.title)) modify it into #set ($discard = $translatedDocument.setcomment('')) References https://jira.xwiki.org/browse/XWIKI-20625 https://github.com/xwiki/xwiki-platform/commit/41d7dca2d30084966ca6a7ee537f39ee8354a7e3 For more information If you have any questions or comments about this advisory: Open an issue in Jira…

Published by the source

19 Dec 2023, 21:39 UTC

Last modified by the source

21 Dec 2023, 21:59 UTC

Source last checked

26 Oct 2026, 16:21 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-p5f8-qf24-24cj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-50732

Advisory: Velocity execution without script right through tree macro
IDs: CVE-2023-50732, GHSA-p5f8-qf24-24cj
Record: https://patchnext.com/advisories/cve-2023-50732 (revision 1, source checked 26 Oct 2026, 16:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.xwiki.platform:xwiki-platform-index-tree-macro 15.2-rc-1, 14.10.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.xwiki.platform:xwiki-platform-index-tree-macro: affected >= 8.3-rc-1, < 14.10.7; >= 15.0-rc-1, < 15.2-rc-1; fixed in 15.2-rc-1, 14.10.7

## Suggested inspection (read-only)
- Maven org.xwiki.platform:xwiki-platform-index-tree-macro: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.xwiki.platform:xwiki-platform-index-tree-macro.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p5f8-qf24-24cj (GitHub-reviewed advisory GHSA-p5f8-qf24-24cj lists affected ranges: Maven org.xwiki.platform:xwiki-platform-index-tree-macro >=8.3-rc-1 =15.0-rc-1 <15.2-rc-1)

Commands are suggestions: review each one before running it.