How severe is CVE-2024-55876?

CVE-2024-55876 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-55876?

CVE-2024-55876 affects the following packages: org.xwiki.platform:xwiki-platform-scheduler-ui (Maven), org.xwiki.platform:xwiki-platform-scheduler-ui (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-55876?

Update org.xwiki.platform:xwiki-platform-scheduler-ui to 15.10.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-55876 is resolved across your whole dependency graph.

How do I detect CVE-2024-55876 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-scheduler-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-55876 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2024-55876 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-55876 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-55876?

CVE-2024-55876 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-55876?

CVE-2024-55876 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-55876 published, and has it been updated?

CVE-2024-55876 was published on December 12, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2024-55876 — xwiki-platform-scheduler-…

MEDIUMFix: xwiki/xwiki-platform@54bcc5a

CVE-2024-55876 is a medium-severity (CVSS 5.4) CWE-862 vulnerability in org.xwiki.platform:xwiki-platform-scheduler-ui. A fix is available for org.xwiki.platform:xwiki-platform-scheduler-ui — see the affected versions and patch details below.

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

Also known asGHSA-cwq6-mjmx-47p6

Published

Dec 12, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-55876.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.xwiki.platform:xwiki-platform-scheduler-ui☕org.xwiki.platform:xwiki-platform-scheduler-ui

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

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.

Patches

This has been patched in XWiki 15.10.9 and 16.3.0.

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

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-scheduler-ui`	≥ 1.2-milestone-2&&< 15.10.9	15.10.9`org.xwiki.platform:xwiki-platform-scheduler-ui:15.10.9`
☕Maven	`org.xwiki.platform:xwiki-platform-scheduler-ui`	≥ 16.0.0-rc-1&&< 16.3.0	16.3.0`org.xwiki.platform:xwiki-platform-scheduler-ui:16.3.0`

Affected Products

1 product · 7 configurations

Application

xwikixwiki

≥ 16.0.0 && < 16.3.0

1 version

1.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-scheduler-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-scheduler-ui to 15.10.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-55876 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact 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. ### Patches This has been patched in XWiki 15.10.9 and 16.3.0. ### 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/54bcc5a7a