CVE-2022-24897

Arbitrary filesystem write access from velocity.

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

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.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2022-24897 has a CVSS score of 7.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (12.6.7, 12.10.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The problem has been patched on versions 12.6.7, 12.10.3 and 13.0RC1.

1. What is CVE-2022-24897? CVE-2022-24897 is a high-severity path traversal vulnerability in org.xwiki.commons:xwiki-commons-velocity (maven), affecting versions >= 2.3.0, < 12.6.7. It is fixed in 12.6.7, 12.10.3. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2022-24897? CVE-2022-24897 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.xwiki.commons:xwiki-commons-velocity are affected by CVE-2022-24897? org.xwiki.commons:xwiki-commons-velocity (maven) versions >= 2.3.0, < 12.6.7 is affected.
4. Is there a fix for CVE-2022-24897? Yes. CVE-2022-24897 is fixed in 12.6.7, 12.10.3. Upgrade to this version or later.
5. Is CVE-2022-24897 exploitable, and should I be worried? Whether CVE-2022-24897 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-24897 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-24897?
   • Upgrade org.xwiki.commons:xwiki-commons-velocity to 12.6.7 or later
   • Upgrade org.xwiki.commons:xwiki-commons-velocity to 12.10.3 or later

Other vulnerabilities in org.xwiki.commons:xwiki-commons-velocity