Arbitrary filesystem write access from velocity.

Exploitation

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

CVSS

7.5 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2022-24897: 1.79% estimated exploitation activity in the next 30 days; percentile 78.39 (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 The velocity scripts is not properly sandboxed against using the Java File API to perform read or write operations on the filesystem. Now writing an attacking script in velocity requires the Script rights in XWiki so not all users can use it, and it also requires finding an XWiki API which returns a File. Patches The problem has been patched on versions 12.6.7, 12.10.3 and 13.0RC1. Workarounds There's no easy workaround for fixing this vulnerability other than upgrading and being careful when giving Script rights. References https://jira.xwiki.org/browse/XWIKI-5168 For more information If you have any questions or comments about this advisory: Open an issue in Jira XWiki Email us at XWiki Security mailing-list

Published by the source

28 Apr 2022, 21:16 UTC

Last modified by the source

30 Jan 2023, 05:00 UTC

Source last checked

26 Oct 2026, 16:02 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cvx5-m8vg-vxgc

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

# Patch Next advisory brief: CVE-2022-24897

Advisory: Arbitrary filesystem write access from velocity.
IDs: CVE-2022-24897, GHSA-cvx5-m8vg-vxgc
Record: https://patchnext.com/advisories/cve-2022-24897 (revision 1, source checked 26 Oct 2026, 16:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.xwiki.commons:xwiki-commons-velocity 12.10.3, 12.6.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.xwiki.commons:xwiki-commons-velocity: affected >= 2.3.0, < 12.6.7; >= 12.7.0, < 12.10.3; fixed in 12.6.7, 12.10.3

## Suggested inspection (read-only)
- Maven org.xwiki.commons:xwiki-commons-velocity: 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.commons:xwiki-commons-velocity.
- 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-cvx5-m8vg-vxgc (GitHub-reviewed advisory GHSA-cvx5-m8vg-vxgc lists affected ranges: Maven org.xwiki.commons:xwiki-commons-velocity >=2.3.0 =12.7.0 <12.10.3)

Commands are suggestions: review each one before running it.