xwiki-platform up to 16.10.5/17.2.x like input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in xwiki-platform up to 16.10.5/17.2.x. It has been rated as problematic. This vulnerability affects the function like. Performing a manipulation results in input validation.
This vulnerability was named CVE-2025-54385. The attack may be initiated remotely. There is no available exploit.
Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in xwiki-platform up to 16.10.5/17.2.x. This affects the function like. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-54385 since 07/21/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Additional levels of successful authentication are necessary for exploitation. Technical details are known, but no exploit is available.
Upgrading to version 16.10.6 or 17.3.0-rc-1 eliminates this vulnerability. Applying the patch 7313dc9b533c70f14b7672379c8b3b63d1fd8f51 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at EUVD (EUVD-2025-22764) and CERT Bund (WID-SEC-2025-1643). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Open Source xwiki
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.1
VulDB Base Score: 4.7
VulDB Temp Score: 4.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: xwiki-platform 16.10.6/17.3.0-rc-1
Patch: 7313dc9b533c70f14b7672379c8b3b63d1fd8f51
Timeline
07/21/2025 CVE reserved07/26/2025 Advisory disclosed
07/26/2025 VulDB entry created
09/04/2025 VulDB entry last update
Sources
Advisory: GHSA-p9qm-p942-q3w5Status: Confirmed
CVE: CVE-2025-54385 (🔒)
GCVE (CVE): GCVE-0-2025-54385
GCVE (VulDB): GCVE-100-317793
EUVD: 🔒
CERT Bund: WID-SEC-2025-1643 - xwiki: Mehrere Schwachstelle ermöglicht eine SQL Injection
Entry
Created: 07/26/2025 07:40Updated: 09/04/2025 01:48
Changes: 07/26/2025 07:40 (69), 07/26/2025 18:17 (7), 07/26/2025 19:48 (1), 09/04/2025 01:48 (12)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.