CVE-2024-56158
BaseFortify
Publication date: 2025-06-12
Last updated on: 2025-09-03
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| xwiki | xwiki | From 1.0 (inc) to 15.10.16 (exc) |
| xwiki | xwiki | From 16.0.0 (inc) to 16.4.7 (exc) |
| xwiki | xwiki | From 16.5.0 (inc) to 16.10.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2024-56158 is a critical SQL injection vulnerability in the XWiki Platform's REST API query endpoint when used with Oracle databases. The vulnerability occurs because the XWiki query validator does not properly sanitize certain SQL functions like DBMS_XMLGEN and DBMS_XMLQUERY. Since Hibernate allows the use of native functions in HQL queries, an attacker can exploit this to execute arbitrary SQL commands remotely without any privileges or user interaction. [1]
How can this vulnerability impact me? :
This vulnerability can have a severe impact as it allows remote attackers to execute arbitrary SQL commands on the database without any privileges or user interaction. This can lead to unauthorized access, modification, or deletion of data, compromising data confidentiality, integrity, and availability. It can also disrupt system operations and potentially lead to a full system compromise. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to upgrade the XWiki Platform to a fixed version: 16.10.1, 16.4.6, or 15.10.16. No known workarounds exist other than upgrading to these patched versions. [1]