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.

357,869

Total vulnerabilities in the database

Vulnerabilities for products matching "strapi"

Found 3 matching products. Filters apply to all results.

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

strapi / strapi

335 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2026-57997	Low	June 29, 2026 6/29/26	< 5.7.0
CVE-2026-27886	Critical	May 14, 2026 5/14/26	>= 4.0.0 < 5.37.0
CVE-2026-22707	Medium	May 14, 2026 5/14/26	< 5.33.3
CVE-2026-22706	Low	May 13, 2026 5/13/26	< 5.33.3
CVE-2026-22599	Critical	May 13, 2026 5/13/26	>= 4.0.0 < 4.26.1 >= 5.0.0 < 5.33.2
CVE-2025-64526	Medium	May 13, 2026 5/13/26	< 5.45.0
CVE-2025-53092	High	October 16, 2025 10/16/25	< 5.20.0
CVE-2025-25298	Medium	October 16, 2025 10/16/25	< 5.10.3
CVE-2024-56143	High	October 16, 2025 10/16/25	>= 5.0.0 < 5.5.2
CVE-2024-52588	Medium	May 27, 2025 5/27/25	< 4.25.2
CVE-2024-37818	High	June 20, 2024 6/20/24	== 4.24.4
CVE-2024-34065	High	June 12, 2024 6/12/24	< 4.24.2
CVE-2024-31217	Medium	June 12, 2024 6/12/24	< 4.22.0
CVE-2024-29181	Low	June 12, 2024 6/12/24	< 4.19.1
CVE-2023-39345	High	November 3, 2023 11/3/23	>= 4.0.0 < 4.13.1
CVE-2023-38507	High	September 13, 2023 9/13/23	< 4.12.1
CVE-2023-37263	Medium	September 13, 2023 9/13/23	< 4.12.1
CVE-2023-36472	Medium	September 13, 2023 9/13/23	< 4.11.7
CVE-2023-34235	High	July 25, 2023 7/25/23	< 4.10.8
CVE-2023-34093	Medium	July 25, 2023 7/25/23	< 4.10.8
CVE-2023-22621	Critical	April 19, 2023 4/19/23	>= 3.0.0 < 4.5.6
CVE-2023-22894	High	April 19, 2023 4/19/23	>= 3.2.1 < 4.8.0
CVE-2023-22893	Medium	April 19, 2023 4/19/23	>= 3.0.0 < 4.6.0
CVE-2022-31367	High	September 28, 2022 9/28/22	>= 4.0.0 < 4.1.10 < 3.6.10
CVE-2022-32114	Medium	July 13, 2022 7/13/22	== 4.1.12
CVE-2022-29894	Medium	June 14, 2022 6/14/22	<= 3.6.10
CVE-2020-13961	Medium	May 24, 2022 5/24/22	< 3.0.2
CVE-2022-30617	High	May 20, 2022 5/20/22	== 4.0.0-beta3 == 4.0.0-beta4 == 4.0.0-beta5 == 4.0.0-beta6 == 4.0.0-beta7 == 4.0.0-beta8 == 4.0.0-beta9 == 4.0.0-beta10 == 4.0.0-beta11 == 4.0.0-beta12 == 4.0.0-beta13 == 4.0.0-beta14 == 4.0.0-beta15 == 4.0.0-beta2 >= 3.0.0 < 3.6.10
CVE-2022-30618	High	May 20, 2022 5/20/22	>= 3.0.0 < 3.6.10 >= 4.0.0 < 4.1.10
CVE-2021-46440	High	May 4, 2022 5/4/22	>= 4.0.0 < 4.1.5 < 3.6.9
CVE-2022-27263	Critical	April 13, 2022 4/13/22	== 4.1.5
CVE-2022-0764	Medium	February 27, 2022 2/27/22	< 4.1.0
CVE-2020-8123	Medium	December 10, 2021 12/10/21	< 3.0.0 == 3.0.0-alpha4 == 3.0.0-alpha4.8 == 3.0.0-alpha5.3 == 3.0.0-alpha5.5 == 3.0.0-alpha6.3 == 3.0.0-alpha6.4 == 3.0.0-alpha6.7 == 3.0.0-alpha7.2 == 3.0.0-alpha7.3 == 3.0.0-alpha8 == 3.0.0-alpha8.3 == 3.0.0-alpha9 == 3.0.0-alpha9.1 == 3.0.0-alpha9.2 == 3.0.0-alpha10.1 == 3.0.0-alpha10.2 == 3.0.0-alpha10.3 == 3.0.0-alpha11 == 3.0.0-alpha11.1 == 3.0.0-alpha11.2 == 3.0.0-alpha11.3 == 3.0.0-alpha12 == 3.0.0-alpha12.1 == 3.0.0-alpha12.1.3 == 3.0.0-alpha12.2 == 3.0.0-alpha12.3 == 3.0.0-alpha12.4 == 3.0.0-alpha12.5 == 3.0.0-alpha12.6 == 3.0.0-alpha12.7 == 3.0.0-alpha12.7.1 == 3.0.0-alpha13 == 3.0.0-alpha13.0.1 == 3.0.0-alpha13.1 == 3.0.0-alpha14 == 3.0.0-alpha14.1 == 3.0.0-alpha14.1.1 == 3.0.0-alpha14.2 == 3.0.0-alpha14.3 == 3.0.0-alpha14.4.0 == 3.0.0-alpha14.5 == 3.0.0-alpha15 == 3.0.0-alpha16 == 3.0.0-alpha17 == 3.0.0-alpha18 == 3.0.0-alpha19 == 3.0.0-alpha20 == 3.0.0-alpha21 == 3.0.0-alpha22 == 3.0.0-alpha23 == 3.0.0-alpha23.1 == 3.0.0-alpha24 == 3.0.0-alpha24.1 == 3.0.0-alpha25 == 3.0.0-alpha25.1 == 3.0.0-alpha25.2 == 3.0.0-alpha26 == 3.0.0-alpha26.1 == 3.0.0-beta0 == 3.0.0-beta1 == 3.0.0-beta2 == 3.0.0-beta3 == 3.0.0-beta4 == 3.0.0-beta5 == 3.0.0-beta6 == 3.0.0-beta7 == 3.0.0-beta8 == 3.0.0-beta9 == 3.0.0-beta10 == 3.0.0-beta11 == 3.0.0-beta12 == 3.0.0-beta13 == 3.0.0-beta14 == 3.0.0-beta15 == 3.0.0-beta16 == 3.0.0-beta16.1 == 3.0.0-beta16.2 == 3.0.0-beta16.3 == 3.0.0-beta16.4 == 3.0.0-beta16.5 == 3.0.0-beta16.6 == 3.0.0-beta16.7 == 3.0.0-beta16.8 == 3.0.0-beta17 == 3.0.0-beta17.1 == 3.0.0-beta17.2 == 3.0.0-beta17.3 == 3.0.0-beta17.4 == 3.0.0-beta17.5 == 3.0.0-beta17.6 == 3.0.0-beta17.7 == 3.0.0-beta17.8 == 3.0.0-beta18 == 3.0.0-beta18.1 == 3.0.0-beta18.2 == 3.0.0-beta18.3 == 3.0.0-alpha26.2
CVE-2021-28128	High	October 6, 2021 10/6/21	<= 3.6.0
CVE-2020-27664	Critical	May 10, 2021 5/10/21	< 3.2.5
CVE-2020-27666	Medium	October 29, 2020 10/29/20	< 3.2.5
CVE-2020-27665	High	October 29, 2020 10/29/20	< 3.2.5
CVE-2019-19609	High	September 4, 2020 9/4/20	<= 1.6.4 == 3.0.0-alpha4.8 == 3.0.0-alpha5.3 == 3.0.0-alpha5.5 == 3.0.0-alpha6.3 == 3.0.0-alpha6.4 == 3.0.0-alpha6.7 == 3.0.0-alpha7.2 == 3.0.0-alpha7.3 == 3.0.0-alpha8 == 3.0.0-alpha8.3 == 3.0.0-alpha9 == 3.0.0-alpha9.1 == 3.0.0-alpha9.2 == 3.0.0-alpha10.1 == 3.0.0-alpha10.2 == 3.0.0-alpha10.3 == 3.0.0-alpha11 == 3.0.0-alpha11.1 == 3.0.0-alpha11.2 == 3.0.0-alpha11.3 == 3.0.0-alpha12 == 3.0.0-alpha12.1 == 3.0.0-alpha12.1.3 == 3.0.0-alpha12.2 == 3.0.0-alpha12.3 == 3.0.0-alpha12.4 == 3.0.0-alpha12.5 == 3.0.0-alpha12.6 == 3.0.0-alpha12.7 == 3.0.0-alpha12.7.1 == 3.0.0-alpha13 == 3.0.0-alpha13.0.1 == 3.0.0-alpha13.1 == 3.0.0-alpha14 == 3.0.0-alpha14.1 == 3.0.0-alpha14.1.1 == 3.0.0-alpha14.2 == 3.0.0-alpha14.3 == 3.0.0-alpha14.4.0 == 3.0.0-alpha14.5 == 3.0.0-alpha15 == 3.0.0-alpha16 == 3.0.0-alpha17 == 3.0.0-alpha18 == 3.0.0-alpha19 == 3.0.0-alpha20 == 3.0.0-alpha21 == 3.0.0-alpha22 == 3.0.0-alpha23 == 3.0.0-alpha23.1 == 3.0.0-alpha24 == 3.0.0-alpha24.1 == 3.0.0-alpha25 == 3.0.0-alpha25.1 == 3.0.0-alpha25.2 == 3.0.0-alpha26 == 3.0.0-alpha26.1 == 3.0.0-beta0 == 3.0.0-beta1 == 3.0.0-beta2 == 3.0.0-beta3 == 3.0.0-beta4 == 3.0.0-beta5 == 3.0.0-beta6 == 3.0.0-beta7 == 3.0.0-beta8 == 3.0.0-beta9 == 3.0.0-beta10 == 3.0.0-beta11 == 3.0.0-beta12 == 3.0.0-beta13 == 3.0.0-beta14 == 3.0.0-beta15 == 3.0.0-beta16 == 3.0.0-beta16.1 == 3.0.0-beta16.2 == 3.0.0-beta16.3 == 3.0.0-beta16.4 == 3.0.0-beta16.5 == 3.0.0-beta16.6 == 3.0.0-beta16.7 == 3.0.0-beta16.8 == 3.0.0-beta17 == 3.0.0-beta17.1 == 3.0.0-beta17.2 == 3.0.0-beta17.3 == 3.0.0-beta17.4 == 3.0.0-beta17.5 == 3.0.0-beta17.6 == 3.0.0-beta17.7 == 3.0.0-alpha4 == 3.0.0-alpha26.2
CVE-2019-18818	Critical	December 2, 2019 12/2/19	<= 1.6.4 == 3.0.0-alpha4.8 == 3.0.0-alpha5.3 == 3.0.0-alpha5.5 == 3.0.0-alpha6.3 == 3.0.0-alpha6.4 == 3.0.0-alpha6.7 == 3.0.0-alpha7.2 == 3.0.0-alpha7.3 == 3.0.0-alpha8 == 3.0.0-alpha8.3 == 3.0.0-alpha9 == 3.0.0-alpha9.1 == 3.0.0-alpha9.2 == 3.0.0-alpha10.1 == 3.0.0-alpha10.2 == 3.0.0-alpha10.3 == 3.0.0-alpha11 == 3.0.0-alpha11.1 == 3.0.0-alpha11.2 == 3.0.0-alpha11.3 == 3.0.0-alpha12 == 3.0.0-alpha12.1 == 3.0.0-alpha12.1.3 == 3.0.0-alpha12.2 == 3.0.0-alpha12.3 == 3.0.0-alpha12.4 == 3.0.0-alpha12.5 == 3.0.0-alpha12.6 == 3.0.0-alpha12.7 == 3.0.0-alpha12.7.1 == 3.0.0-alpha13 == 3.0.0-alpha13.0.1 == 3.0.0-alpha13.1 == 3.0.0-alpha14 == 3.0.0-alpha14.1 == 3.0.0-alpha14.1.1 == 3.0.0-alpha14.2 == 3.0.0-alpha14.3 == 3.0.0-alpha14.4.0 == 3.0.0-alpha14.5 == 3.0.0-alpha15 == 3.0.0-alpha16 == 3.0.0-alpha17 == 3.0.0-alpha18 == 3.0.0-alpha19 == 3.0.0-alpha20 == 3.0.0-alpha21 == 3.0.0-alpha22 == 3.0.0-alpha23 == 3.0.0-alpha23.1 == 3.0.0-alpha24 == 3.0.0-alpha24.1 == 3.0.0-alpha25 == 3.0.0-alpha25.1 == 3.0.0-alpha25.2 == 3.0.0-alpha26 == 3.0.0-alpha26.1 == 3.0.0-beta0 == 3.0.0-beta1 == 3.0.0-beta2 == 3.0.0-beta3 == 3.0.0-beta4 == 3.0.0-beta5 == 3.0.0-beta6 == 3.0.0-beta7 == 3.0.0-beta8 == 3.0.0-beta9 == 3.0.0-beta10 == 3.0.0-beta11 == 3.0.0-beta12 == 3.0.0-beta13 == 3.0.0-beta14 == 3.0.0-beta15 == 3.0.0-beta16 == 3.0.0-beta16.1 == 3.0.0-beta16.2 == 3.0.0-beta16.3 == 3.0.0-beta16.4 == 3.0.0-beta16.5 == 3.0.0-beta16.6 == 3.0.0-beta16.7 == 3.0.0-beta16.8 == 3.0.0-beta17 == 3.0.0-beta17.1 == 3.0.0-beta17.2 == 3.0.0-beta17.3 == 3.0.0-beta17.4 == 3.0.0-alpha4 == 3.0.0-alpha26.2

strapi

13 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-31367	High	September 28, 2022 9/28/22	< 3.6.10
CVE-2022-29894	Medium	June 14, 2022 6/14/22	<= 3.6.10
CVE-2020-13961	Medium	May 24, 2022 5/24/22	< 3.0.2
CVE-2022-30617	High	May 20, 2022 5/20/22	>= 3.0.0 < 3.6.9
CVE-2022-30618	High	May 20, 2022 5/20/22	>= 3.0.0 < 3.6.9
CVE-2021-46440	High	May 4, 2022 5/4/22	< 3.6.9
CVE-2022-27263	Critical	April 13, 2022 4/13/22	<= 4.1.5
CVE-2022-0764	Medium	February 27, 2022 2/27/22	< 4.1.0
CVE-2021-28128	High	October 6, 2021 10/6/21	<= 3.6.0
CVE-2020-27664	Critical	May 10, 2021 5/10/21	< 3.2.5
CVE-2019-19609	High	September 4, 2020 9/4/20	< 3.0.0-beta.17.8
Command Injection in strapi	High	September 4, 2020 9/4/20	< 3.0.0-beta.17.8
CVE-2019-18818	Critical	December 2, 2019 12/2/19	< 3.0.0-beta.17.5

@strapi / strapi

11 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2026-27886	Critical	May 14, 2026 5/14/26	>= 4.0.0 < 5.37.0
CVE-2025-3930	Medium	October 16, 2025 10/16/25	< 5.24.1
CVE-2024-37818	High	June 20, 2024 6/20/24	== 4.24.4
CVE-2023-39345	High	November 3, 2023 11/3/23	>= 4.0.0 < 4.13.1
CVE-2023-34093	Medium	July 25, 2023 7/25/23	< 4.10.8
CVE-2023-22894	High	April 19, 2023 4/19/23	>= 3.2.1 < 4.8.0
CVE-2022-31367	High	September 28, 2022 9/28/22	>= 4.0.0-next.0 < 4.1.10
CVE-2022-32114	Medium	July 13, 2022 7/13/22	<= 4.1.12
CVE-2022-30617	High	May 20, 2022 5/20/22	< 4.0.0-beta.15
CVE-2022-30618	High	May 20, 2022 5/20/22	< 4.1.9
CVE-2021-46440	High	May 4, 2022 5/4/22	>= 4.0.0 < 4.1.5

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