Summary
XWiki Platform: Remote code execution through space title and Solr space facet
Workarounds
Modify the Main.SolrSpaceFacet page following this patch.
References
Impact
By creating a document with a specially crafted title, it is possible to trigger remote code execution in the (Solr-based) search in XWiki. This allows any user who can edit the title of a space (all users by default) to execute any Groovy code in the XWiki installation which compromises the confidentiality, integrity and availability of the whole XWiki installation.
To reproduce, as a user without script nor programming rights, create a document with title {{/html}}{{async}}{{groovy}}println("Hello from Groovy Title!"){{/groovy}}{{/async}} and content Test Document. Using the search UI, search for "Test Document", then deploy the Location facet on the right of the screen, next to the search results. The installation is vulnerable if you see an item such as:
Hello from Groovy Title!
</a>
<div class="itemCount">1</div>
</li>
</ul>
{{/html}}
Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.
CVE-2024-31984 has a CVSS score of 9.9 (Critical). 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 (14.10.20, 15.5.4, 15.10-rc-1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This has been patched in XWiki 14.10.20, 15.5.4 and 15.10 RC1.
Frequently Asked Questions
- What is CVE-2024-31984? CVE-2024-31984 is a critical-severity code injection vulnerability in org.xwiki.platform:xwiki-platform-search-solr-ui (maven), affecting versions >= 7.2-rc-1, < 14.10.20. It is fixed in 14.10.20, 15.5.4, 15.10-rc-1. Untrusted input is evaluated as executable code within the application's runtime environment.
- How severe is CVE-2024-31984? CVE-2024-31984 has a CVSS score of 9.9 (Critical). 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.
- Which versions of org.xwiki.platform:xwiki-platform-search-solr-ui are affected by CVE-2024-31984? org.xwiki.platform:xwiki-platform-search-solr-ui (maven) versions >= 7.2-rc-1, < 14.10.20 is affected.
- Is there a fix for CVE-2024-31984? Yes. CVE-2024-31984 is fixed in 14.10.20, 15.5.4, 15.10-rc-1. Upgrade to this version or later.
- Is CVE-2024-31984 exploitable, and should I be worried? Whether CVE-2024-31984 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
- What actually determines whether CVE-2024-31984 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.
- How do I fix CVE-2024-31984?
- Upgrade
org.xwiki.platform:xwiki-platform-search-solr-uito 14.10.20 or later - Upgrade
org.xwiki.platform:xwiki-platform-search-solr-uito 15.5.4 or later - Upgrade
org.xwiki.platform:xwiki-platform-search-solr-uito 15.10-rc-1 or later
- Upgrade