Summary
Json response for search reveals Solr credentials
Workarounds
None.
References
Impact
An error in Ibexa's Solr search engine results in potential exposure of Solr credentials. This is a critical vulnerability and all supported versions of the engine are affected. Those not using the Solr search engine are not affected.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The issue is fixed in all supported versions of ibexa/solr, see "Patched versions".
An advisory is also published for ezsystems/ezplatform-solr-search-engine, please see that repository.
Commit: https://github.com/ibexa/solr/commit/2f8b711874bee1ebe31fb8a6362e0c8e52c53012
Frequently Asked Questions
- What is GHSA-V6XP-CCVX-W52M? GHSA-V6XP-CCVX-W52M is a critical-severity security vulnerability in ibexa/solr (composer), affecting versions >= 4.5.0, < 4.5.4. It is fixed in 4.5.4.
- Which versions of ibexa/solr are affected by GHSA-V6XP-CCVX-W52M? ibexa/solr (composer) versions >= 4.5.0, < 4.5.4 is affected.
- Is there a fix for GHSA-V6XP-CCVX-W52M? Yes. GHSA-V6XP-CCVX-W52M is fixed in 4.5.4. Upgrade to this version or later.
- Is GHSA-V6XP-CCVX-W52M exploitable, and should I be worried? Whether GHSA-V6XP-CCVX-W52M is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-V6XP-CCVX-W52M is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-V6XP-CCVX-W52M? Upgrade
ibexa/solrto 4.5.4 or later.