How severe is GHSA-4wxw-42wx-2wfx?

No CVSS score has been assigned to GHSA-4wxw-42wx-2wfx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4wxw-42wx-2wfx?

GHSA-4wxw-42wx-2wfx affects the following packages: org.apache.solr:solr-core (Maven), org.apache.solr:solr-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-4wxw-42wx-2wfx?

Update org.apache.solr:solr-core to 9.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4wxw-42wx-2wfx is resolved across your whole dependency graph.

How do I detect GHSA-4wxw-42wx-2wfx in my Maven dependencies?

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

How do I mitigate GHSA-4wxw-42wx-2wfx 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.

How does O3 Security protect against GHSA-4wxw-42wx-2wfx?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4wxw-42wx-2wfx can be triaged on real exposure rather than presence alone.

Is GHSA-4wxw-42wx-2wfx actively exploited in the wild?

No public exploit code has been indexed for GHSA-4wxw-42wx-2wfx 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-4wxw-42wx-2wfx?

GHSA-4wxw-42wx-2wfx has an EPSS (Exploit Prediction Scoring System) score of 3.0%, placing it in the 87th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4wxw-42wx-2wfx?

GHSA-4wxw-42wx-2wfx is classified as CWE-732 (CWE-732). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4wxw-42wx-2wfx published, and has it been updated?

GHSA-4wxw-42wx-2wfx was published on February 9, 2024 and was last updated on December 6, 2024. 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

GHSA-4wxw-42wx-2wfx — solr-core

Fix: apache/lucene-solr@6e9ed20

GHSA-4wxw-42wx-2wfx is a CWE-732 vulnerability in org.apache.solr:solr-core. A fix is available for org.apache.solr:solr-core — see the affected versions and patch details below.

Apache Solr Schema Designer blindly "trusts" all configsets

Also known asBIT-solr-2023-50292CVE-2023-50292

Published

Feb 9, 2024

Updated

Dec 6, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-4wxw-42wx-2wfx.

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

☕org.apache.solr:solr-core☕org.apache.solr:solr-core

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

Incorrect Permission Assignment for Critical Resource, Improper Control of Dynamically-Managed Code Resources vulnerability in Apache Solr.

This issue affects Apache Solr from 8.10.0 through 8.11.2, from 9.0.0 before 9.3.0.

The Schema Designer was introduced to allow users to more easily configure and test new Schemas and configSets. However, when the feature was created, the "trust" (authentication) of these configSets was not considered. External library loading is only available to configSets that are "trusted" (created by authenticated users), thus non-authenticated users are unable to perform Remote Code Execution. Since the Schema Designer loaded configSets without taking their "trust" into account, configSets that were created by unauthenticated users were allowed to load external libraries when used in the Schema Designer.

Users are recommended to upgrade to version 9.3.0 or 8.11.3, both of which fix the issue.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.solr:solr-core`	≥ 9.0.0&&< 9.3.0	9.3.0`org.apache.solr:solr-core:9.3.0`
☕Maven	`org.apache.solr:solr-core`	≥ 8.10.0&&< 8.11.3	8.11.3`org.apache.solr:solr-core:8.11.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.apache.solr:solr-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.solr:solr-core to 9.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4wxw-42wx-2wfx 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 O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4wxw-42wx-2wfx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-4wxw-42wx-2wfx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Incorrect Permission Assignment for Critical Resource, Improper Control of Dynamically-Managed Code Resources vulnerability in Apache Solr. This issue affects Apache Solr from 8.10.0 through 8.11.2, from 9.0.0 before 9.3.0. The Schema Designer was introduced to allow users to more easily configure and test new Schemas and configSets. However, when the feature was created, the "trust" (authentication) of these configSets was not considered. External library loading is only available to configSets that are "trusted" (created by authenticated users), thus non-authenticated users are unable to p

O3 Security · Impact-Aware SCA

Is GHSA-4wxw-42wx-2wfx in your dependencies?

O3 Security finds GHSA-4wxw-42wx-2wfx across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works