dbcve.org
XwikiApplication

CVE-2024-21651

MEDIUM · 6.5 CVSS v3.1 Published 2024-01-09
Fix available
A fix is available. Upgrade to 14.10.18 / 15.5.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 offering runtime services for applications built on top of it. A user able to attach a file to a page can post a malformed TAR file by manipulating file modification times headers, which when parsed by Tika, could cause a denial of service issue via CPU consumption. This vulnerability has been patched in XWiki 14.10.18, 15.5.3 and 15.8 RC1.

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 · high confidence

A user with file attachment permissions can upload a malformed TAR file with manipulated file modification time headers. When XWiki's Tika parser processes this file, it causes excessive CPU consumption leading to denial of service.

MitigationUpgrade XWiki to version 14.10.18, 15.5.3, or 15.8 or later. Until patched, consider restricting or temporarily disabling file upload permissions for untrusted users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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:>= 14.10, < 14.10.18>= 15.5, < 15.5.3>= 15.6, < 15.8

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
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify XWiki version
    Log into XWiki as admin, go to Administration > Information, or check the version in the footer of any page. Alternatively, examine the WEB-INF/lib directory for xwiki-platform-core jars with version metadata.
    Affected if The installed version falls within >= 14.10 and < 14.10.18, OR >= 15.5 and < 15.5.3, OR >= 15.6 and < 15.8.
  2. Verify Tika parser is active
    Check the XWiki configuration file xwiki.cfg or examine the file viewer service configuration. The Tika parser is typically invoked when viewing office documents or attachments that require content extraction. Look for tika-parser or related parser implementations in the classpath.
    Affected if The Tika parser module is deployed and enabled in the XWiki instance.
  3. Confirm file attachment upload is permitted
    Navigate to Administration > Rights, or examine the XWiki.XWikiRights objects via the API. Check if users other than admin have the 'attach' permission on any space or the main wiki.
    Affected if Non-admin users or untrusted accounts possess file attachment/upload permissions.

If the XWiki version is in the affected ranges AND the Tika parser is enabled AND users with file upload permissions exist, the environment is vulnerable to this DoS.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.18 / 15.5.3 / 15.8 or later
Fixed in 14.10.1815.5.315.8
Interim mitigation

Upgrade XWiki to version 14.10.18, 15.5.3, or 15.8 or later. Until patched, consider restricting or temporarily disabling file upload permissions for untrusted users.

Recommended fix High confidence

XWiki 14.10.18, 15.5.3, or 15.8+ depending on your current branch

  1. 1. Identify the currently running XWiki version by checking the application footer or administration dashboard.
  2. 2. Determine which release branch your current version belongs to (14.10.x, 15.5.x, or 15.6-15.7.x).
  3. 3. For 14.10.x branch: Upgrade to version 14.10.18 or later.
  4. 4. For 15.5.x branch: Upgrade to version 15.5.3 or later.
  5. 5. For 15.6-15.7.x branch: Upgrade to version 15.8 or later.
  6. 6. Download the appropriate WAR file or use your package manager to perform the upgrade.
  7. 7. Backup your database and wiki data before proceeding.
  8. 8. Deploy the new version and verify the application starts successfully.

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

Fix this in Xwiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-21651 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