How severe is GHSA-2grh-gr37-2283?

GHSA-2grh-gr37-2283 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2grh-gr37-2283?

GHSA-2grh-gr37-2283 affects the following packages: org.xwiki.platform:xwiki-platform-search-solr-api (Maven), org.xwiki.platform:xwiki-platform-search-solr-api (Maven), org.xwiki.platform:xwiki-platform-search-solr-api (Maven). Ecosystems affected: Maven.

How do I fix GHSA-2grh-gr37-2283?

Update org.xwiki.platform:xwiki-platform-search-solr-api to 14.10.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2grh-gr37-2283 is resolved across your whole dependency graph.

How do I detect GHSA-2grh-gr37-2283 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-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2grh-gr37-2283 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-2grh-gr37-2283 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2grh-gr37-2283 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 GHSA-2grh-gr37-2283?

GHSA-2grh-gr37-2283 has an EPSS (Exploit Prediction Scoring System) score of 59.1%, 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 GHSA-2grh-gr37-2283?

GHSA-2grh-gr37-2283 is classified as Information Exposure (CWE-200). 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 GHSA-2grh-gr37-2283?

A Nuclei detection template exists for GHSA-2grh-gr37-2283, 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 GHSA-2grh-gr37-2283 published, and has it been updated?

GHSA-2grh-gr37-2283 was published on December 16, 2023 and was last updated on September 10, 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

MEDIUM severity

Solr search discloses email addresses of usersGHSA-2grh-gr37-2283

MEDIUMFix: xwiki/xwiki-platform@3e5272f

GHSA-2grh-gr37-2283 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in org.xwiki.platform:xwiki-platform-search-solr-api. EPSS puts its 30-day exploitation probability at 59.1% (99th percentile). A fix is available for org.xwiki.platform:xwiki-platform-search-solr-api — see the affected versions and patch details below.

Also known asCVE-2023-50720

Published

Dec 16, 2023

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

59.1%probability of exploitation in next 30 days

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

3 pkgs affected

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

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 in XWiki discloses the email addresses of users even when obfuscation of email addresses is enabled. To demonstrate the vulnerability, search for objcontent:email* using XWiki's regular search interface.

Patches

This has been fixed in XWiki 14.10.15, 15.5.2 and 15.7RC1 by not indexing email address properties when obfuscation is enabled. Further, changing the setting now triggers re-indexing of the affected wiki(s).

Workarounds

We're not aware of any workarounds.

References

Attribution

This vulnerability was reported on Intigriti by ynoof @Ynoof5.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-search-solr-api`	all versions	14.10.15`org.xwiki.platform:xwiki-platform-search-solr-api:14.10.15`
☕Maven	`org.xwiki.platform:xwiki-platform-search-solr-api`	≥ 15.0-rc-1&&< 15.5.2	15.5.2`org.xwiki.platform:xwiki-platform-search-solr-api:15.5.2`
☕Maven	`org.xwiki.platform:xwiki-platform-search-solr-api`	≥ 15.6-rc-1&&< 15.7-rc-1	15.7-rc-1`org.xwiki.platform:xwiki-platform-search-solr-api:15.7-rc-1`

Affected Products

1 product · 5 configurations

Application

xwikixwiki

≥ 15.0 && < 15.5.2

2 versions

15.615.7

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-api, 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-api to 14.10.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2grh-gr37-2283 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

How to detect GHSA-2grh-gr37-2283

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

nuclei -id ghsa-2grh-gr37-2283 -u https://target

Template: XWiki < 4.10.15 - Email Disclosure
Severity: medium
Impact: Successful exploitation could lead to disclosure of the email of all the users.
Remediation: This has been fixed in XWiki 14.10.15, 15.5.2 and 15.7RC1 by not indexing email address properties when obfuscation is enabled.

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 in XWiki discloses the email addresses of users even when obfuscation of email addresses is enabled. To demonstrate the vulnerability, search for `objcontent:email*` using XWiki's regular search interface. ### Patches This has been fixed in XWiki 14.10.15, 15.5.2 and 15.7RC1 by not indexing email address properties when obfuscation is enabled. Further, changing the setting now triggers re-indexing of the affected wiki(s). ### Workarounds We're not aware of any workarounds. ### References * https://jira.xwiki.org/browse/XWIKI-20371 * https://github.com/xwiki/