How severe is GHSA-ww97-9w65-2crx?

GHSA-ww97-9w65-2crx has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-ww97-9w65-2crx?

GHSA-ww97-9w65-2crx affects the following packages: org.apache.solr:solr-core (Maven), org.apache.solr:solr-core (Maven), org.apache.solr:solr-core (Maven), org.apache.solr:solr-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-ww97-9w65-2crx?

Update org.apache.solr:solr-core to 8.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ww97-9w65-2crx is resolved across your whole dependency graph.

How do I detect GHSA-ww97-9w65-2crx 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-ww97-9w65-2crx 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-ww97-9w65-2crx actively exploited in the wild?

Yes. There are 12 known exploit references for GHSA-ww97-9w65-2crx, including 2 documented proof-of-concept exploits on Exploit-DB and 9 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-ww97-9w65-2crx?

GHSA-ww97-9w65-2crx has an EPSS (Exploit Prediction Scoring System) score of 98.6%, placing it in the 100th 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.

Is GHSA-ww97-9w65-2crx in the CISA Known Exploited Vulnerabilities catalog?

Yes. GHSA-ww97-9w65-2crx (Apache Solr VelocityResponseWriter Plug-In Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is GHSA-ww97-9w65-2crx?

GHSA-ww97-9w65-2crx is classified as CWE-74 (CWE-74). 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-ww97-9w65-2crx?

A Nuclei detection template exists for GHSA-ww97-9w65-2crx, 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-ww97-9w65-2crx published, and has it been updated?

GHSA-ww97-9w65-2crx was published on February 12, 2020 and was last updated on October 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

Improper Input Validation in Apache SolrGHSA-ww97-9w65-2crx

HIGHFix: apache/lucene-solr#1156

GHSA-ww97-9w65-2crx is a high-severity (CVSS 7.5) CWE-74 vulnerability in org.apache.solr:solr-core. It is in CISA's Known Exploited Vulnerabilities catalog (added 2021-11-03) — treat it as actively exploited and patch now. A fix is available for org.apache.solr:solr-core — see the affected versions and patch details below.

Also known asCVE-2019-17558

Published

Feb 12, 2020

Updated

Oct 22, 2025

Affected

4 pkgs

Patched

4 / 4

Exploits

12 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2021-11-03. Federal agencies were required to remediate by 2022-05-03.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for GHSA-ww97-9w65-2crx.

EPSS Exploitation Probability

via FIRST.org ↗

98.6%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-ww97-9w65-2crx by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

4 pkgs affected

☕org.apache.solr:solr-core☕org.apache.solr:solr-core☕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

Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter. A Velocity template can be provided through Velocity templates in a configset velocity/ directory or as a parameter. A user defined configset could contain renderable, potentially malicious, templates. Parameter provided templates are disabled by default, but can be enabled by setting params.resource.loader.enabled by defining a response writer with that setting set to true. Defining a response writer requires configuration API access. Solr 8.4 removed the params resource loader entirely, and only enables the configset-provided template rendering when the configset is trusted (has been uploaded by an authenticated user).

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.solr:solr-core`	≥ 5.0.0&&< 8.4.0	8.4.0`org.apache.solr:solr-core:8.4.0`
☕Maven	`org.apache.solr:solr-core`	≥ 6.0.0&&< 8.4.0	8.4.0`org.apache.solr:solr-core:8.4.0`
☕Maven	`org.apache.solr:solr-core`	≥ 7.0.0&&< 8.4.0	8.4.0`org.apache.solr:solr-core:8.4.0`
☕Maven	`org.apache.solr:solr-core`	≥ 8.0.0&&< 8.4.0	8.4.0`org.apache.solr:solr-core:8.4.0`

Affected Products

2 products · 7 configurations

Application

solrapache

≥ 8.0.0 && < 8.4.0

range

Application

primavera unifieroracle

≥ 17.7 && ≤ 17.12

4 versions

16.116.218.819.12

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-47572webappsjava

Apache Solr 8.2.0 - Remote Code Execution

by @l3x_wong · Nov 1, 2019

Exploit-DB Source

EDB-48338remotemultiple✓ Verified

Apache Solr - Remote Code Execution via Velocity Template (Metasploit)

by Metasploit · Apr 16, 2020

Exploit-DB Source

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 8.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ww97-9w65-2crx 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 to detect GHSA-ww97-9w65-2crx

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

nuclei -id ghsa-ww97-9w65-2crx -u https://target

Template: Apache Solr <=8.3.1 - Remote Code Execution
Severity: high
Impact: Successful exploitation of this vulnerability allows an attacker to execute arbitrary code on the affected system.
Remediation: Upgrade to a patched version of Apache Solr (8.4.0 or later) to mitigate this vulnerability.

Template by ProjectDiscovery nuclei-templates (pikpikcu, madrobot), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter. A Velocity template can be provided through Velocity templates in a configset `velocity/` directory or as a parameter. A user defined configset could contain renderable, potentially malicious, templates. Parameter provided templates are disabled by default, but can be enabled by setting `params.resource.loader.enabled` by defining a response writer with that setting set to `true`. Defining a response writer requires configuration API access. Solr 8.4 removed the params resource

O3 Security · Impact-Aware SCA

Is GHSA-ww97-9w65-2crx in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works