Skip to content
Fencer Vulns
high 7.5

CVE-2023-48241 in the critical feed json

XWiki exposed whole content of all documents of all wikis to anybody with view right on Solr suggest service

published 2023-11-20 2 y ago modified 2026-09-10 1 mo ago also GHSA-7fqr-97j7-jgf4 , EUVD-2023-2908

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
72.8%
EPSS 72.8% chance of exploitation in 30 days, percentile 99.4%
public exploits
0
none known, plus a Nuclei check

Summary

XWiki Platform is a generic wiki platform. Starting in version 6.3-milestone-2 and prior to versions 14.10.15, 15.5.1, and 15.6RC1, the Solr-based search suggestion provider that also duplicates as generic JavaScript API for search results in XWiki exposes the content of all documents of all wikis to anybody who has access to it, by default it is public. This exposes all information stored in the wiki (but not some protected information like password hashes). While there is a right check normally, the right check can be circumvented by explicitly requesting fields from Solr that don't include the data for the right check. This has been fixed in XWiki 15.6RC1, 15.5.1 and 14.10.15 by not listing documents whose rights cannot be checked. No known workarounds are available.

Patch / fix

  • maven org.xwiki.platform:xwiki-platform-search-solr-query 14.10.15, 15.5.1
  • xwiki xwiki 14.10.5, 15.5.1

Exploit prediction

72.82% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.xwiki.platform:xwiki-platform-search-solr-query
>=6.3-milestone-2, <14.10.15
>=15.0-rc-1, <15.5.1
14.10.15
15.5.1

Affected products

  • xwiki xwiki-platform

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.