Summary
XWiki allows RCE from script right in configurable sections
Workarounds
We're not aware of any workaround except upgrading.
References
- https://jira.xwiki.org/browse/XWIKI-21207
- https://github.com/xwiki/xwiki-platform/commit/8493435ff9606905a2d913607d6c79862d0c168d
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira XWiki.org
- Email us at Security Mailing List
Impact
Any user with script rights can perform arbitrary remote code execution by adding instances of XWiki.ConfigurableClass to any page. This compromises the confidentiality, integrity and availability of the whole XWiki installation.
To reproduce on a instance, as a user with script rights, edit your user profile and add an object of type XWiki.ConfigurableClass ("Custom configurable sections").
Set "Display in section" and "Display in category" to other, "Scope" to Wiki and all spaces and "Heading" to:
#set($codeToExecute = 'Test') #set($codeToExecuteResult = '{{async}}{{groovy}}services.logging.getLogger("attacker").error("Attack from Heading succeeded!"){{/groovy}}{{/async}}')
Save the page and view it, then add ?sheet=XWiki.AdminSheet&viewer=content§ion=other to the URL.
If the logs contain "attacker - Attack from Heading succeeded!", then the instance is vulnerable.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
CVE-2024-55879 has a CVSS score of 9.1 (Critical). The vector is network-reachable, high 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 (15.10.9, 16.3.0); 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 15.10.9 and 16.3.0.
Frequently Asked Questions
- What is CVE-2024-55879? CVE-2024-55879 is a critical-severity missing authorization vulnerability in org.xwiki.platform:xwiki-platform-administration-ui (maven), affecting versions >= 2.3, < 15.10.9. It is fixed in 15.10.9, 16.3.0. The application does not perform an authorization check before performing a sensitive operation.
- How severe is CVE-2024-55879? CVE-2024-55879 has a CVSS score of 9.1 (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-administration-ui are affected by CVE-2024-55879? org.xwiki.platform:xwiki-platform-administration-ui (maven) versions >= 2.3, < 15.10.9 is affected.
- Is there a fix for CVE-2024-55879? Yes. CVE-2024-55879 is fixed in 15.10.9, 16.3.0. Upgrade to this version or later.
- Is CVE-2024-55879 exploitable, and should I be worried? Whether CVE-2024-55879 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-55879 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-55879?
- Upgrade
org.xwiki.platform:xwiki-platform-administration-uito 15.10.9 or later - Upgrade
org.xwiki.platform:xwiki-platform-administration-uito 16.3.0 or later
- Upgrade