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.

325,773

Total vulnerabilities in the database

Vulnerabilities for products matching "redcap"

Found 3 matching products. Filters apply to all results.

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

vanderbilt / redcap

41 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2024-55374	Medium	January 2, 2026 1/2/26	== 14.3.13
CVE-2024-37396	Medium	June 10, 2025 6/10/25	< 14.2.1
CVE-2024-37395	Medium	June 10, 2025 6/10/25	< 14.2.1
CVE-2024-37394	Medium	June 10, 2025 6/10/25	< 14.2.1
CVE-2025-23113	Low	January 10, 2025 1/10/25	== 14.9.6
CVE-2025-23110	Medium	January 10, 2025 1/10/25	== 14.9.6
CVE-2025-23111	Low	January 10, 2025 1/10/25	== 14.9.6
CVE-2025-23112	Medium	January 10, 2025 1/10/25	== 14.9.6
CVE-2024-56377	Medium	January 9, 2025 1/9/25	== 14.9.6
CVE-2024-56376	Medium	January 9, 2025 1/9/25	== 14.9.6
CVE-2024-56314	Medium	December 22, 2024 12/22/24	<= 14.9.6
CVE-2024-56313	Medium	December 22, 2024 12/22/24	<= 14.9.6
CVE-2024-56312	Medium	December 22, 2024 12/22/24	<= 14.9.6
CVE-2024-56311	High	December 22, 2024 12/22/24	<= 14.9.6
CVE-2024-56310	High	December 22, 2024 12/22/24	<= 14.9.6
CVE-2024-45527	Medium	September 2, 2024 9/2/24	== 14.7.0
CVE-2023-38825	Medium	March 21, 2024 3/21/24	< 13.8.0
CVE-2023-37798	Medium	September 7, 2023 9/7/23	<= 13.1.35
CVE-2023-37361	Low	July 25, 2023 7/25/23	< 12.3.2 < 12.0.26
CVE-2022-42715	Medium	October 12, 2022 10/12/22	>= 12.5.0 < 12.5.11 < 12.4.18
CVE-2022-24004	Medium	June 15, 2022 6/15/22	== 12.0.11
CVE-2022-24127	Medium	June 15, 2022 6/15/22	== 12.0.11
CVE-2021-42136	Critical	April 13, 2022 4/13/22	< 11.4.0
CVE-2020-26712	Critical	January 12, 2021 1/12/21	== 10.3.4 == 10.0.20
CVE-2020-26713	Medium	January 12, 2021 1/12/21	== 10.3.4 == 10.0.20
CVE-2020-27358	Low	November 2, 2020 11/2/20	>= 8.11.6 < 10.0
CVE-2019-17121	Medium	October 4, 2019 10/4/19	< 9.3.4
CVE-2019-15127	Low	August 21, 2019 8/21/19	< 9.3.0
CVE-2019-14937	Medium	August 17, 2019 8/17/19	>= 8.11.5 < 9.3.0
CVE-2019-13029	Low	July 11, 2019 7/11/19	>= 9.0 < 9.1.2 >= 8.0 < 8.10.2
CVE-2017-7351	Low	February 8, 2018 2/8/18	>= 7.0.0 < 7.0.11
CVE-2017-10961	Medium	July 18, 2017 7/18/17	<= 7.5.0
CVE-2017-10962	Low	July 18, 2017 7/18/17	<= 7.5.0
CVE-2013-4608	Low	June 17, 2013 6/17/13	== 4.14.4 <= 5.0.5 == 4.14.3 == 4.14.0 == 4.14.2 == 4.14.1
CVE-2013-4609	Medium	June 17, 2013 6/17/13	== 4.14.4 <= 5.0.3 == 4.14.3 == 4.14.0 == 4.14.2 == 4.14.1
CVE-2013-4610	High	June 17, 2013 6/17/13	== 4.14.4 <= 5.0.2 == 4.14.3 == 4.14.0 == 4.14.2 == 4.14.1
CVE-2013-4611	High	June 17, 2013 6/17/13	== 4.14.4 <= 5.1.0 == 4.14.3 == 4.14.0 == 4.14.2 == 4.14.1
CVE-2013-4612	Low	June 17, 2013 6/17/13	== 4.14.4 <= 5.0.6 == 4.14.3 == 4.14.0 == 4.14.2 == 4.14.1
CVE-2012-6564	Low	June 17, 2013 6/17/13	<= 4.14.4 == 4.14.3 == 4.14.0 == 4.14.2 == 4.14.1
CVE-2012-6565	Low	June 17, 2013 6/17/13	<= 4.14.2 == 4.14.0 == 4.14.1
CVE-2012-6566	Low	June 17, 2013 6/17/13	<= 4.14.1 == 4.14.0

project-redcap / redcap

6 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2013-4608	Low	June 17, 2013 6/17/13	== 4.15.4 == 4.15.2 == 4.14.6 == 5.0.3 == 4.14.5 == 5.0.1 == 5.0.4 == 4.13.18 == 4.15.3 == 4.15.1 == 4.15.0 == 5.0.0 == 5.0.2
CVE-2013-4609	Medium	June 17, 2013 6/17/13	== 5.1.0 == 5.1.1 == 4.15.4 == 4.15.2 == 4.14.6 == 4.14.5 == 5.0.1 == 5.1.2 == 4.13.18 == 4.15.3 == 4.15.1 == 4.15.0 == 5.0.0 == 5.0.2
CVE-2013-4610	High	June 17, 2013 6/17/13	== 5.1.0 == 5.1.1 == 4.15.4 == 4.15.2 == 4.14.6 == 4.14.5 == 5.0.1 == 5.0.6 == 4.13.18 == 4.15.3 == 4.15.1 == 4.15.0 == 5.0.0
CVE-2013-4611	High	June 17, 2013 6/17/13	== 5.0.5 == 4.15.4 == 4.15.2 == 4.14.6 == 5.0.3 == 4.14.5 == 5.0.1 == 5.0.6 == 5.0.4 == 4.13.18 == 4.15.3 == 4.15.1 == 4.15.0 == 5.0.0 == 5.0.2
CVE-2013-4612	Low	June 17, 2013 6/17/13	== 5.0.5 == 4.15.4 == 4.15.2 == 4.14.6 == 5.0.3 == 4.14.5 == 5.0.1 == 5.0.4 == 4.13.18 == 4.15.3 == 4.15.1 == 4.15.0 == 5.0.0 == 5.0.2
CVE-2012-6567	Medium	June 17, 2013 6/17/13	<= 4.13.18

evms / redcap

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2020-27359	Medium		November 2, 2020 11/2/20	>= 8.11.6 < 10.0.0

Showing vulnerabilities for 3 products matching "redcap". 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.