dbcve.org
XwikiApplication

CVE-2025-54385

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-26
Fix available
A fix is available. Upgrade to 16.10.6 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 Platform is a generic wiki platform offering runtime services for applications built on top of it. In versions between 17.0.0-rc1 to 17.2.2 and versions 16.10.5 and below, it's possible to execute any SQL query in Oracle by using the function like DBMS_XMLGEN or DBMS_XMLQUERY. The XWiki#searchDocuments APIs pass queries directly to Hibernate without sanitization. Even when these APIs enforce a specific SELECT clause, attackers can still inject malicious code through HQL's native function support in other parts of the query (such as the WHERE clause). This is fixed in versions 16.10.6 and 17.3.0-rc-1.

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 Platform contains a SQL injection vulnerability in the XWiki#searchDocuments APIs that pass queries directly to Hibernate without sanitization. Attackers can inject malicious SQL through HQL's native function support (e.g., DBMS_XMLGEN or DBMS_XMLQUERY in Oracle databases) even when SELECT clauses are enforced, allowing execution of arbitrary SQL queries.

MitigationUpgrade to XWiki version 16.10.6 or 17.3.0-rc-1 (or later) to patch the SQL injection vulnerability.

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:< 16.10.6>= 17.0.0, <= 17.2.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 installed XWiki version
    Check the version through the XWiki admin interface (Administer > Info) or by locating the xwiki-platform-core jar file and checking its version metadata
    Affected if The installed version is less than 16.10.6 OR falls between 17.0.0 and 17.2.2 inclusive
  2. Determine the database backend in use
    Check the hibernate.cfg.xml or configuration.properties file for the database connection settings, or view the database type from the XWiki admin dashboard
    Affected if The backend database is Oracle (the specific HQL native function exploit targets Oracle's DBMS_XMLGEN or DBMS_XMLQUERY)
  3. Identify usage of searchDocuments API
    Search application logs and code for calls to XWiki#searchDocuments or org.xwiki.model.XWiki#searchDocuments method invocations
    Affected if The searchDocuments API is actively used or exposed, which would allow injection of malicious HQL queries
  4. Review database access permissions
    Check the database user permissions configured for XWiki in the connection settings; verify if the database user has privileges beyond read-only access
    Affected if The XWiki database user has elevated privileges (such as execute on UTL_FILE or similar Oracle packages) that could be exploited for further impact

You are affected if your XWiki version is below 16.10.6 or between 17.0.0 and 17.2.2, and you use an Oracle database backend with the searchDocuments API accessible to potential attackers.

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 16.10.6 or later
Fixed in 16.10.6
Vendor patch github.com →
Interim mitigation

Upgrade to XWiki version 16.10.6 or 17.3.0-rc-1 (or later) to patch the SQL injection vulnerability.

Recommended fix High confidence

16.10.6 or 17.3.0-rc-1 (or later stable releases within respective branches)

  1. 1. Identify the current XWiki version by checking the application administration or the pom.xml/version file
  2. 2. Confirm the version is affected: versions below 16.10.6 OR between 17.0.0 and 17.2.2 (inclusive) are vulnerable
  3. 3. If using Oracle database with the XWiki#searchDocuments API or HQL queries, this vulnerability is exploitable
  4. 4. Back up the current XWiki installation and database before upgrading
  5. 5. For installations using version 16.x: upgrade to version 16.10.6 or later stable (e.g., 16.10.7, 16.10.x latest)
  6. 6. For installations using version 17.x: upgrade to version 17.3.0-rc-1 or later stable (e.g., 17.3.0, 17.4.0, or 17.x latest)
  7. 7. Verify the upgrade was successful by checking the XWiki version in the administration interface
  8. 8. Review the XWiki release notes for the target version to check for any breaking changes or required migration steps
Caveat Review XWiki release notes for the target version; minor version upgrades typically have minimal breaking changes but custom extensions or configurations may require adjustments

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 / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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