How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "solr"

Found 3 matching products. Filters apply to all results.

You can search for specific versions with /product/solr/1.2.3

apache / solr

46 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2026-22022	High	January 21, 2026 1/21/26	>= 5.3.0 < 9.10.1
CVE-2026-22444	High	January 21, 2026 1/21/26	>= 8.6.0 < 9.10.1
CVE-2025-24814	Medium	January 27, 2025 1/27/25	< 9.8.0
CVE-2024-52012	Medium	January 27, 2025 1/27/25	>= 6.6.0 < 9.8.0
CVE-2024-45217	High	October 16, 2024 10/16/24	>= 9.0.0 < 9.7.0 >= 6.6.0 < 8.11.4
CVE-2024-45216	Critical	October 16, 2024 10/16/24	>= 5.3.0 < 8.11.4 >= 9.0.0 < 9.7.0
CVE-2023-50386	High	February 9, 2024 2/9/24	>= 6.0.0 < 8.11.3 >= 9.0.0 < 9.4.1
CVE-2023-50298	High	February 9, 2024 2/9/24	>= 6.0.0 < 8.11.3 >= 9.0.0 < 9.4.1
CVE-2023-50292	High	February 9, 2024 2/9/24	>= 6.0.0 < 8.11.3 >= 9.0.0 < 9.4.1
CVE-2023-50291	High	February 9, 2024 2/9/24	>= 9.0.0 < 9.3.0 >= 6.0.0 < 8.11.3
CVE-2023-50290	Medium	January 15, 2024 1/15/24	>= 9.0.0 < 9.3.0
CVE-2023-44487	High	October 10, 2023 10/10/23	< 9.4.0
CVE-2021-44548	Critical	December 23, 2021 12/23/21	< 8.11.1
CVE-2021-33813	High	June 16, 2021 6/16/21	== 8.8.1 == 8.9
CVE-2021-27905	Critical	April 13, 2021 4/13/21	< 8.8.2
CVE-2021-29262	High	April 13, 2021 4/13/21	< 8.8.2
CVE-2021-29943	Critical	April 13, 2021 4/13/21	< 8.8.2
CVE-2021-28163	Low	April 1, 2021 4/1/21	== 8.8.1
CVE-2020-27223	Medium	February 26, 2021 2/26/21	== 8.8.1
CVE-2020-9492	High	January 26, 2021 1/26/21	== 8.6.0 == 8.6.2
CVE-2020-13957	Critical	October 13, 2020 10/13/20	>= 8.0.0 <= 8.6.2 >= 7.0.0 <= 7.7.3 >= 6.6.0 <= 6.6.6
CVE-2020-13941	High	August 17, 2020 8/17/20	< 8.6.0
CVE-2018-11802	Low	April 1, 2020 4/1/20	< 6.6.6 >= 7.0.0 < 7.7.0
CVE-2019-17558	High	December 30, 2019 12/30/19	>= 8.0.0 < 8.4.0 >= 5.0.0 < 7.7.3
CVE-2019-12409	Critical	November 18, 2019 11/18/19	== 8.1.1 == 8.2.0
CVE-2019-12401	High	September 10, 2019 9/10/19	>= 4.0.0 <= 4.10.4 >= 3.1 <= 3.6.2 >= 1.3.0 <= 1.4.1
CVE-2019-0193	High	August 1, 2019 8/1/19	>= 8.1.0 < 8.1.2 < 7.7.3
CVE-2017-3164	Medium	March 8, 2019 3/8/19	>= 1.3.0 <= 7.6.0
CVE-2019-0192	High	March 7, 2019 3/7/19	>= 6.0.0 <= 6.6.5 >= 5.0.0 <= 5.5.5
CVE-2018-8026	Low	July 5, 2018 7/5/18	>= 7.0.0 <= 7.3.1 >= 6.0.0.x <= 6.6.4
CVE-2018-8010	Low	May 21, 2018 5/21/18	>= 6.0.0 <= 6.6.3 >= 7.0.0 <= 7.3.0
CVE-2018-1308	Medium	April 9, 2018 4/9/18	>= 7.0.0 <= 7.2.1 >= 1.2 <= 6.6.2
CVE-2017-1000190	Critical	November 17, 2017 11/17/17	== 8.4.1
CVE-2017-12629	Critical	October 14, 2017 10/14/17	>= 5.5.0 <= 5.5.4 >= 6.0.0 <= 6.6.1 >= 7.0.0 <= 7.0.1
CVE-2017-9803	Medium	September 18, 2017 9/18/17	== 6.2.1 == 6.4.0 == 6.2.0 == 6.4.1 == 6.5.0 == 6.4.2 == 6.5.1 == 6.3.0 == 6.6.0
CVE-2017-3163	Medium	August 30, 2017 8/30/17	== 6.2.1 <= 5.5.3 == 6.0.0 == 6.0.1 == 6.1.0 == 6.4.0 == 6.2.0 == 6.3.0
CVE-2017-7660	Medium	July 7, 2017 7/7/17	== 6.2.1 == 6.0.0 == 5.5.0 == 6.0.1 == 5.3.2 == 6.1.0 == 5.4.1 == 6.4.0 == 6.2.0 == 5.5.4 == 5.5.3 == 5.4.0 == 6.4.1 == 6.5.0 == 6.4.2 == 6.5.1 == 5.5.1 == 5.5.2 == 5.3.1 == 5.3.0 == 6.3.0
CVE-2015-8797	Low	February 15, 2016 2/15/16	<= 5.3
CVE-2015-8796	Low	February 15, 2016 2/15/16	<= 5.2.1
CVE-2015-8795	Low	February 15, 2016 2/15/16	<= 5.0
CVE-2014-3628	Low	January 6, 2015 1/6/15	== 4.5.0 == 4.7.1 == 4.10.2 == 4.0.0-alpha == 4.6.1 == 4.2.1 == 4.10.1 == 4.3.0 == 4.8.0 == 4.9.1 == 4.0.0-beta == 4.7.2 == 4.4.0 == 4.2.0 == 4.6.0 == 4.5.1 == 4.3.1 == 4.7.0 == 4.0.0 == 4.10.0 == 4.8.1 == 4.1.0 == 4.9.0
CVE-2012-6612	High	December 7, 2013 12/7/13	== 4.0.0-alpha == 4.0.0-beta <= 4.0.0
CVE-2013-6397	Low	December 7, 2013 12/7/13	== 4.5.0 == 4.0.0-alpha <= 4.5.1 == 4.2.1 == 4.3.0 == 4.0.0-beta == 4.4.0 == 4.2.0 == 4.3.1 == 4.0.0 == 4.1.0
CVE-2013-6407	Medium	December 7, 2013 12/7/13	== 4.0.0-alpha == 3.6.1 == 3.6.0 == 4.0.0-beta <= 4.0.0 == 3.6.2
CVE-2013-6408	Medium	December 7, 2013 12/7/13	== 4.0.0-alpha == 3.6.1 == 4.2.1 == 3.6.0 == 4.0.0-beta == 4.2.0 == 3.6.2 == 4.0.0 == 4.1.0 <= 4.3.0
CVE-2009-3821	Low	October 28, 2009 10/28/09	== 1.0.0

org.apache.solr / solr

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2014-3628	Low		January 6, 2015 1/6/15	>= 4.0.0 < 4.10.3

ibexa / solr

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
Json response for search reveals Solr credentials	Critical		November 3, 2023 11/3/23	>= 4.5.0 < 4.5.4

Showing vulnerabilities for 3 products matching "solr". Each product has independent pagination.

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.