Summary
XWiki Platform document history including authors of any page exposed to unauthorized actors
Workarounds
There aren't any known workarounds apart from upgrading to a fixed version.
References
Impact
The REST API exposes the history of any page in XWiki of which the attacker knows the name. The exposed information includes for each modification of the page the time of the modification, the version number, the author of the modification (both username and displayed name) and the version comment. This information is exposed regardless of the rights setup, and even when the wiki is configured to be fully private.
On a private wiki, this can be tested by accessing /xwiki/rest/wikis/xwiki/spaces/Main/pages/WebHome/history, if this shows the history of the main page then the installation 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-45591 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no 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-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 15.10.9 and XWiki 16.3.0RC1.
Frequently Asked Questions
- What is CVE-2024-45591? CVE-2024-45591 is a medium-severity missing authorization vulnerability in org.xwiki.platform:xwiki-platform-rest-server (maven), affecting versions >= 1.8.0, < 15.10.9. It is fixed in 15.10.9, 16.3.0-rc-1. The application does not perform an authorization check before performing a sensitive operation.
- How severe is CVE-2024-45591? CVE-2024-45591 has a CVSS score of 5.3 (Medium). 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-rest-server are affected by CVE-2024-45591? org.xwiki.platform:xwiki-platform-rest-server (maven) versions >= 1.8.0, < 15.10.9 is affected.
- Is there a fix for CVE-2024-45591? Yes. CVE-2024-45591 is fixed in 15.10.9, 16.3.0-rc-1. Upgrade to this version or later.
- Is CVE-2024-45591 exploitable, and should I be worried? Whether CVE-2024-45591 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-45591 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-45591?
- Upgrade
org.xwiki.platform:xwiki-platform-rest-serverto 15.10.9 or later - Upgrade
org.xwiki.platform:xwiki-platform-rest-serverto 16.3.0-rc-1 or later
- Upgrade