How severe is CVE-2020-13957?

CVE-2020-13957 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-13957?

CVE-2020-13957 affects the following packages: org.apache.solr:solr-parent (Maven), org.apache.solr:solr-solrj (Maven), org.apache.solr:solr-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-13957?

Update org.apache.solr:solr-parent to 8.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-13957 is resolved across your whole dependency graph.

How do I detect CVE-2020-13957 in my Maven dependencies?

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

How do I mitigate CVE-2020-13957 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2020-13957 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-13957 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 CVE-2020-13957?

CVE-2020-13957 has an EPSS (Exploit Prediction Scoring System) score of 79.3%, 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.

What type of vulnerability is CVE-2020-13957?

CVE-2020-13957 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-13957 published, and has it been updated?

CVE-2020-13957 was published on October 13, 2020 and was last updated on October 24, 2026. 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

CRITICAL severity

CVE-2020-13957 — solr-parent

CRITICALFix: apache/solr@e001c22

CVE-2020-13957 is a critical-severity (CVSS 9.8) CWE-863 vulnerability in org.apache.solr:solr-parent. EPSS puts its 30-day exploitation probability at 79.3% (100th percentile). A fix is available for org.apache.solr:solr-parent — see the affected versions and patch details below.

Incorrect Authorization in Apache Solr

Also known asBIT-solr-2020-13957GHSA-3c7p-vv5r-cmr5

Published

Oct 13, 2020

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

79.3%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

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.apache.solr:solr-parent☕org.apache.solr:solr-solrj☕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 versions 6.6.0 to 6.6.6, 7.0.0 to 7.7.3 and 8.0.0 to 8.6.2 prevents some features considered dangerous (which could be used for remote code execution) to be configured in a ConfigSet that's uploaded via API without authentication/authorization. The checks in place to prevent such features can be circumvented by using a combination of UPLOAD/CREATE actions. This issue is patched in 8.6.3.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.solr:solr-parent`	≥ 6.6.0&&< 8.6.3	8.6.3`org.apache.solr:solr-parent:8.6.3`
☕Maven	`org.apache.solr:solr-solrj`	≥ 6.6.0&&< 8.6.3	8.6.3`org.apache.solr:solr-solrj:8.6.3`
☕Maven	`org.apache.solr:solr-core`	≥ 6.6.0&&< 8.6.3	8.6.3`org.apache.solr:solr-core:8.6.3`

Affected Products

1 product · 3 configurations

Application

solrapache

≥ 8.0.0 && ≤ 8.6.2

range

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-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.solr:solr-parent to 8.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-13957 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-13957 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works