XwikiApplication

CVE-2024-31984

HIGH · 8.8 CVSS v3.1 Published 2024-04-10
Fix available
A fix is available. Upgrade to 14.10.20 / 15.5.4 or later.
See remediation →
94/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
XWiki Platform is a generic wiki platform. Starting in version 7.2-rc-1 and prior to versions 4.10.20, 15.5.4, and 15.10-rc-1, by creating a document with a specially crafted title, it is possible to trigger remote code execution in the (Solr-based) search in XWiki. This allows any user who can edit the title of a space (all users by default) to execute any Groovy code in the XWiki installation which compromises the confidentiality, integrity and availability of the whole XWiki installation. This has been patched in XWiki 14.10.20, 15.5.4 and 15.10 RC1. As a workaround, manually apply the patch to the `Main.SolrSpaceFacet` page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
XwikiApplication
Affected:>= 7.3, < 14.10.20>= 15.0, < 15.5.4>= 15.6, < 15.10= 7.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 14.10.20 / 15.5.4 / 15.10 or later
Fixed in 14.10.2015.5.415.10
Vendor patch github.com →
Recommended fix High confidence

XWiki 14.10.20, 15.5.4, or 15.10+ (depending on your current major version branch)

  1. Identify your current XWiki version from the affected versions list (7.2, >= 7.3 to < 14.10.20, >= 15.0 to < 15.5.4, or >= 15.6 to < 15.10)
  2. Backup your XWiki database and configuration files
  3. Stop the XWiki application
  4. Upgrade to one of the fixed releases: XWiki 14.10.20, 15.5.4, or 15.10 (or later within your major version line)
  5. Follow the standard XWiki upgrade documentation for your deployment method
  6. Start the XWiki application and verify functionality
  7. As an alternative workaround (if immediate upgrade is not possible), manually apply the patch from commit 43c9d551e3c11e9d8f176b556dd33bbe31fc66e0 to the Main.SolrSpaceFacet page in your wiki
Caveat Review XWiki release notes for your target version to check for any breaking changes between your current and target version; minor version upgrades within the same major line typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31984 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-31984 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data