CVE-2024-55876

XWiki's scheduler in subwiki allows scheduling operations for any main wiki user

Workarounds

If you have subwikis where the Job Scheduler is enabled, you can edit the objects on Scheduler.WebPreferences to match https://github.com/xwiki/xwiki-platform/commit/54bcc5a7a2e440cc591b91eece9c13dc0c487331#diff-8e274bd0065e319a34090339de6dfe56193144d15fd71c52c1be7272254728b4.

References

• https://jira.xwiki.org/browse/XWIKI-21663
• https://github.com/xwiki/xwiki-platform/commit/54bcc5a7a2e440cc591b91eece9c13dc0c487331

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

Any user with an account on the main wiki could run scheduling operations on subwikis.
To reproduce, as a user on the main wiki without any special right, view the document Scheduler.WebHome in a subwiki. Then, click on any operation (e.g., Trigger) on any job. If the operation is successful, 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-55876 has a CVSS score of 5.4 (Medium). 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 (15.10.9, 16.3.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

This has been patched in XWiki 15.10.9 and 16.3.0.

1. What is CVE-2024-55876? CVE-2024-55876 is a medium-severity missing authorization vulnerability in org.xwiki.platform:xwiki-platform-scheduler-ui (maven), affecting versions >= 1.2-milestone-2, < 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.
2. How severe is CVE-2024-55876? CVE-2024-55876 has a CVSS score of 5.4 (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.
3. Which versions of org.xwiki.platform:xwiki-platform-scheduler-ui are affected by CVE-2024-55876? org.xwiki.platform:xwiki-platform-scheduler-ui (maven) versions >= 1.2-milestone-2, < 15.10.9 is affected.
4. Is there a fix for CVE-2024-55876? Yes. CVE-2024-55876 is fixed in 15.10.9, 16.3.0. Upgrade to this version or later.
5. Is CVE-2024-55876 exploitable, and should I be worried? Whether CVE-2024-55876 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-2024-55876 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-2024-55876?
   • Upgrade org.xwiki.platform:xwiki-platform-scheduler-ui to 15.10.9 or later
   • Upgrade org.xwiki.platform:xwiki-platform-scheduler-ui to 16.3.0 or later

Other vulnerabilities in org.xwiki.platform:xwiki-platform-scheduler-ui