How severe is GHSA-v6xp-ccvx-w52m?

No CVSS score has been assigned to GHSA-v6xp-ccvx-w52m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v6xp-ccvx-w52m?

GHSA-v6xp-ccvx-w52m affects the following packages: ibexa/solr (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-v6xp-ccvx-w52m?

Update ibexa/solr to 4.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v6xp-ccvx-w52m is resolved across your whole dependency graph.

How do I detect GHSA-v6xp-ccvx-w52m in my Packagist dependencies?

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

How do I mitigate GHSA-v6xp-ccvx-w52m 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 GHSA-v6xp-ccvx-w52m actively exploited in the wild?

No public exploit code has been indexed for GHSA-v6xp-ccvx-w52m 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.

When was GHSA-v6xp-ccvx-w52m published, and has it been updated?

GHSA-v6xp-ccvx-w52m was published on November 3, 2023 and was last updated on December 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Json response for search reveals Solr credentialsGHSA-v6xp-ccvx-w52m

Fix: ibexa/solr@2f8b711

GHSA-v6xp-ccvx-w52m is a security vulnerability in ibexa/solr. A fix is available for ibexa/solr — see the affected versions and patch details below.

Published

Nov 3, 2023

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 4, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘ibexa/solr

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

Description

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.

Patches

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

Workarounds

None.

References

https://developers.ibexa.co/security-advisories/ibexa-sa-2023-005-vulnerabilities-in-solr-search-and-file-downloads

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ibexa/solr`	≥ 4.5.0&&< 4.5.4	4.5.4`composer require ibexa/solr:^4.5.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ibexa/solr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ibexa/solr to 4.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v6xp-ccvx-w52m 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.

Frequently Asked Questions

### 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. ### Patches 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 ### Workarounds None. ### References https://developers.ibexa.co/s

O3 Security · Impact-Aware SCA

Is GHSA-v6xp-ccvx-w52m in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works