How severe is GHSA-45w3-2hvv-pfxq?

No CVSS score has been assigned to GHSA-45w3-2hvv-pfxq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-45w3-2hvv-pfxq?

GHSA-45w3-2hvv-pfxq affects the following packages: org.apache.solr:solr-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-45w3-2hvv-pfxq?

Update org.apache.solr:solr-core to 4.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-45w3-2hvv-pfxq is resolved across your whole dependency graph.

How do I detect GHSA-45w3-2hvv-pfxq 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-45w3-2hvv-pfxq 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-45w3-2hvv-pfxq?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-45w3-2hvv-pfxq can be triaged on real exposure rather than presence alone.

Is GHSA-45w3-2hvv-pfxq actively exploited in the wild?

No public exploit code has been indexed for GHSA-45w3-2hvv-pfxq 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-45w3-2hvv-pfxq?

GHSA-45w3-2hvv-pfxq has an EPSS (Exploit Prediction Scoring System) score of 11.4%, placing it in the 96th 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 warrants monitoring and prompt remediation.

When was GHSA-45w3-2hvv-pfxq published, and has it been updated?

GHSA-45w3-2hvv-pfxq was published on May 17, 2022 and was last updated on November 30, 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-45w3-2hvv-pfxq — solr-core

Fix: apache/lucene-solr@7239a57

GHSA-45w3-2hvv-pfxq is a security vulnerability in org.apache.solr:solr-core. EPSS puts its 30-day exploitation probability at 11.4% (96th percentile). A fix is available for org.apache.solr:solr-core — see the affected versions and patch details below.

XML Injection in Apache Solr

Also known asCVE-2013-6408

Published

May 17, 2022

Updated

Nov 30, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

11.4%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% 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

1 pkg affected

☕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

The DocumentAnalysisRequestHandler in Apache Solr before 4.3.1 does not properly use the EmptyEntityResolver, which allows remote attackers to have an unspecified impact via XML data containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue. NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-6407.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.solr:solr-core`	all versions	4.3.1`org.apache.solr:solr-core:4.3.1`

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 4.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-45w3-2hvv-pfxq 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-45w3-2hvv-pfxq can be triaged on real exposure rather than presence alone.

Tailored to GHSA-45w3-2hvv-pfxq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat JBoss Data Grid 6.2	`solr`	RHSA-2014:0029
Red Hat JBoss Web Framework Kit 2.4	`solr`	RHSA-2013:1844

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-45w3-2hvv-pfxq in your dependencies?

O3 Security finds GHSA-45w3-2hvv-pfxq 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