dbcve.org
XwikiApplication

CVE-2024-56158

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-12
Fix available
A fix is available. Upgrade to 15.10.16 / 16.4.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 is a generic wiki platform. It's possible to execute any SQL query in Oracle by using the function like DBMS_XMLGEN or DBMS_XMLQUERY. The XWiki query validator does not sanitize functions that would be used in a simple select and Hibernate allows using any native function in an HQL query. This vulnerability is fixed in 16.10.2, 16.4.7, and 15.10.16.

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

XWiki has a critical SQL injection vulnerability in Oracle databases where the query validator fails to sanitize Oracle-specific functions (DBMS_XMLGEN, DBMS_XMLQUERY) that can be used in HQL queries, allowing arbitrary SQL execution.

MitigationUpgrade XWiki to version 16.10.2, 16.4.7, or 15.10.16 to patch the query validator and Hibernate function handling.

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:>= 1.0, < 15.10.16>= 16.0.0, < 16.4.7>= 16.5.0, < 16.10.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
    Locate the version file or check the about page in the XWiki administration (typically at /xwiki/bin/view/About). The version is usually displayed in the footer or in the administration dashboard under 'Information'.
    Affected if The installed version falls within < 15.10.16, >= 16.0.0 and < 16.4.7, or >= 16.5.0 and < 16.10.2.
  2. Confirm database type
    Check the XWiki configuration file (hibernate.cfg.xml or properties file in the WEB-INF directory) for the database connection settings. Look for the 'hibernate.dialect' or database URL configuration.
    Affected if The database is Oracle (dialect shows Oracle or URL contains 'oracle' in the driver/database name).
  3. Verify query validator exposure
    Review application logs or test environment to confirm that HQL (Hibernate Query Language) queries can be submitted through XWiki's API, macros, or user-editable content that gets parsed into HQL.
    Affected if HQL query execution is possible (this is the default behavior in XWiki for many features including search, documents, and user management).

You are affected if your XWiki version is in the vulnerable ranges AND you are using an Oracle database, because the unpatched query validator does not sanitize Oracle-specific functions in HQL queries.

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 15.10.16 / 16.4.7 / 16.10.2 or later
Fixed in 15.10.1616.4.716.10.2
Vendor patch github.com →
Interim mitigation

Upgrade XWiki to version 16.10.2, 16.4.7, or 15.10.16 to patch the query validator and Hibernate function handling.

Recommended fix High confidence

16.10.2 (recommended latest stable release; alternatively 15.10.16 for 15.x branch or 16.4.7 for 16.0-16.4 branch)

  1. 1. Backup your current XWiki database and installation directory before proceeding with the upgrade.
  2. 2. Download the fixed version appropriate for your current installation branch: 15.10.16 (for 15.x users), 16.4.7 (for 16.0-16.4 users), or 16.10.2 (for 16.5+ users).
  3. 3. Follow the official XWiki upgrade documentation for your deployment method (WAR or Docker). For WAR: stop the application server, replace the WAR file, restart. For Docker: pull the new image and recreate the container with your existing data volume.
  4. 4. Clear any caching mechanisms (database query cache, application caches) after upgrade to ensure the patched code is active.
  5. 5. Verify the installation by checking the XWiki version at xwiki/bin/view/XWiki/XWikiPreferences and confirming Oracle database queries work correctly.
Caveat Review XWiki release notes between your current version and target version for any configuration or database migration requirements; major version jumps may require migration steps.

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

Fix this in Xwiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-56158 — 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-56158 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