How severe is GHSA-j2r6-r929-v6gf?

GHSA-j2r6-r929-v6gf 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 GHSA-j2r6-r929-v6gf?

GHSA-j2r6-r929-v6gf affects the following packages: org.xwiki.platform:xwiki-platform-scheduler-ui (Maven), org.xwiki.platform:xwiki-platform-scheduler-ui (Maven), org.xwiki.platform:xwiki-platform-scheduler-ui (Maven). Ecosystems affected: Maven.

How do I fix GHSA-j2r6-r929-v6gf?

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

How do I detect GHSA-j2r6-r929-v6gf 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 GHSA-j2r6-r929-v6gf if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-j2r6-r929-v6gf actively exploited in the wild?

No public exploit code has been indexed for GHSA-j2r6-r929-v6gf 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 GHSA-j2r6-r929-v6gf?

GHSA-j2r6-r929-v6gf has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th 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 GHSA-j2r6-r929-v6gf?

GHSA-j2r6-r929-v6gf is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j2r6-r929-v6gf published, and has it been updated?

GHSA-j2r6-r929-v6gf was published on April 10, 2024 and was last updated on September 10, 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

XWiki Platform CSRF in the job schedulerGHSA-j2r6-r929-v6gf

MEDIUMFix: xwiki/xwiki-platform@8a92cb4

GHSA-j2r6-r929-v6gf is a medium-severity (CVSS 5.4) Cross-Site Request Forgery (CSRF) 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.

Also known asCVE-2024-31985

Published

Apr 10, 2024

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-j2r6-r929-v6gf.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs24th percentile — riskier than 24% 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

3 pkgs affected

☕org.xwiki.platform:xwiki-platform-scheduler-ui☕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

It is possible to schedule/trigger/unschedule existing jobs by having an admin visit the Job Scheduler page through a predictable URL, for example by embedding such an URL in any content as an image.

To reproduce in an XWiki installation, open <xwiki-host>:/xwiki/bin/view/Scheduler/?do=trigger&which=Scheduler.NotificationEmailDailySender as a user with admin rights. If there is no error message that indicates the CSRF token is invalid, the installation is vulnerable.

Patches

The vulnerability has been fixed on XWiki 14.10.19, 15.5.5, and 15.9.

Workarounds

Modify the Scheduler.WebHome page following this patch.

References

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-scheduler-ui`	≥ 3.1&&< 14.10.19	14.10.19`org.xwiki.platform:xwiki-platform-scheduler-ui:14.10.19`
☕Maven	`org.xwiki.platform:xwiki-platform-scheduler-ui`	≥ 15.0-rc-1&&< 15.5.4	15.5.4`org.xwiki.platform:xwiki-platform-scheduler-ui:15.5.4`
☕Maven	`org.xwiki.platform:xwiki-platform-scheduler-ui`	≥ 15.6-rc-1&&< 15.9	15.9`org.xwiki.platform:xwiki-platform-scheduler-ui:15.9`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 15.6 && < 15.9

range

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 14.10.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j2r6-r929-v6gf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact It is possible to schedule/trigger/unschedule existing jobs by having an admin visit the Job Scheduler page through a predictable URL, for example by embedding such an URL in any content as an image. To reproduce in an XWiki installation, open `<xwiki-host>:/xwiki/bin/view/Scheduler/?do=trigger&which=Scheduler.NotificationEmailDailySender` as a user with admin rights. If there is no error message that indicates the CSRF token is invalid, the installation is vulnerable. ### Patches The vulnerability has been fixed on XWiki 14.10.19, 15.5.5, and 15.9. ### Workarounds Modify the Sch