How severe is CVE-2023-48241?

CVE-2023-48241 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-48241?

CVE-2023-48241 affects the following packages: org.xwiki.platform:xwiki-platform-search-solr-query (Maven), org.xwiki.platform:xwiki-platform-search-solr-query (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-48241?

Update org.xwiki.platform:xwiki-platform-search-solr-query to 14.10.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-48241 is resolved across your whole dependency graph.

How do I detect CVE-2023-48241 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-search-solr-query, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-48241 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2023-48241 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-48241 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-48241?

CVE-2023-48241 has an EPSS (Exploit Prediction Scoring System) score of 72.8%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2023-48241?

CVE-2023-48241 is classified as CWE-285 (CWE-285). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2023-48241?

A Nuclei detection template exists for CVE-2023-48241, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2023-48241 published, and has it been updated?

CVE-2023-48241 was published on November 20, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2023-48241 — xwiki-platform-search-sol…

HIGHFix: xwiki/xwiki-platform@93b8ec7

CVE-2023-48241 is a high-severity (CVSS 7.5) CWE-285 vulnerability in org.xwiki.platform:xwiki-platform-search-solr-query. EPSS puts its 30-day exploitation probability at 72.8% (99th percentile). A fix is available for org.xwiki.platform:xwiki-platform-search-solr-query — see the affected versions and patch details below.

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

Also known asGHSA-7fqr-97j7-jgf4

Published

Nov 20, 2023

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

72.8%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.xwiki.platform:xwiki-platform-search-solr-query☕org.xwiki.platform:xwiki-platform-search-solr-query

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

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 can be reproduced by opening <xwiki-server>/xwiki/bin/get/XWiki/SuggestSolrService?outputSyntax=plain&media=json&nb=1000&query=q%3D*%3A*%0Aq.op%3DAND%0Afq%3Dtype%3ADOCUMENT%0Afl%3Dtitle_%2C+reference%2C+links%2C+doccontentraw_%2C+objcontent__&input=+ where <xwiki-server> is the URL of the XWiki installation. If this displays any results, the wiki is vulnerable.

Patches

This has been fixed in XWiki 15.6RC1, 15.5.1 and 14.10.15 by not listing documents whose rights cannot be checked.

Workarounds

We're not aware of a workaround apart from upgrading to a fixed version.

References

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-search-solr-query`	≥ 6.3-milestone-2&&< 14.10.15	14.10.15`org.xwiki.platform:xwiki-platform-search-solr-query:14.10.15`
☕Maven	`org.xwiki.platform:xwiki-platform-search-solr-query`	≥ 15.0-rc-1&&< 15.5.1	15.5.1`org.xwiki.platform:xwiki-platform-search-solr-query:15.5.1`

Affected Products

1 product · 4 configurations

Application

xwikixwiki

≥ 15.0 && < 15.5.1

1 version

6.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-search-solr-query, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-search-solr-query to 14.10.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-48241 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect CVE-2023-48241

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2023-48241 -u https://target

Template: XWiki < 4.10.15 - Information Disclosure
Severity: high
Impact: Successful exploitation could lead to disclosure of content of all documents of all wikis.

Template by ProjectDiscovery nuclei-templates (ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Impact 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 can be reproduced by opening `<xwiki-server>/xwiki/bin/get/XWiki/SuggestSolrService?ou