Vulnerability Database

326,895

Total vulnerabilities in the database

Vulnerabilities for products matching "parse--server"

Found 2 matching products. Filters apply to all results.

You can search for specific versions with /product/parse--server/1.2.3

parseplatform / parse-server

32 vulnerabilities found
Title Severity Exploit Date Affected Version
Critical February 25, 2026 2/25/26
< 8.6.3
>= 9.0.0 < 9.3.1
== 9.3.1-alpha1
== 9.3.1-alpha2
== 9.3.1-alpha3
Medium December 16, 2025 12/16/25
< 8.6.2
== 9.0.0
== 9.0.0-alpha1
== 9.0.0-alpha10
== 9.0.0-alpha11
== 9.0.0-alpha2
== 9.0.0-alpha3
== 9.0.0-alpha4
== 9.0.0-alpha5
== 9.0.0-alpha6
== 9.0.0-alpha7
== 9.0.0-alpha8
== 9.0.0-alpha9
== 9.1.0
== 9.1.0-alpha1
== 9.1.0-alpha2
== 9.1.0-alpha3
== 9.1.0-alpha4
Medium December 16, 2025 12/16/25
< 8.6.1
== 9.0.0
== 9.0.0-alpha1
== 9.0.0-alpha10
== 9.0.0-alpha11
== 9.0.0-alpha2
== 9.0.0-alpha3
== 9.0.0-alpha4
== 9.0.0-alpha5
== 9.0.0-alpha6
== 9.0.0-alpha7
== 9.0.0-alpha8
== 9.0.0-alpha9
== 9.1.0-alpha1
== 9.1.0-alpha2
Critical December 12, 2025 12/12/25
<= 8.5.0
== 8.6.0-alpha1
High October 4, 2024 10/4/24
< 6.5.9
>= 7.0.0 < 7.3.0
Critical March 19, 2024 3/19/24
< 6.5.5
== 7.0.0-alpha1
== 7.0.0-alpha10
== 7.0.0-alpha11
== 7.0.0-alpha12
== 7.0.0-alpha13
== 7.0.0-alpha14
== 7.0.0-alpha15
== 7.0.0-alpha16
== 7.0.0-alpha17
== 7.0.0-alpha18
== 7.0.0-alpha19
== 7.0.0-alpha2
== 7.0.0-alpha20
== 7.0.0-alpha21
== 7.0.0-alpha22
== 7.0.0-alpha23
== 7.0.0-alpha24
== 7.0.0-alpha25
== 7.0.0-alpha26
== 7.0.0-alpha27
== 7.0.0-alpha28
== 7.0.0-alpha3
== 7.0.0-alpha4
== 7.0.0-alpha5
== 7.0.0-alpha6
== 7.0.0-alpha7
== 7.0.0-alpha8
== 7.0.0-alpha9
Critical March 1, 2024 3/1/24
< 6.5.0
== 6.5.0-alpha1
== 6.5.0-alpha2
== 6.5.0-beta1
== 7.0.0-alpha1
== 7.0.0-alpha10
== 7.0.0-alpha11
== 7.0.0-alpha12
== 7.0.0-alpha13
== 7.0.0-alpha14
== 7.0.0-alpha15
== 7.0.0-alpha16
== 7.0.0-alpha17
== 7.0.0-alpha18
== 7.0.0-alpha19
== 7.0.0-alpha2
== 7.0.0-alpha3
== 7.0.0-alpha4
== 7.0.0-alpha5
== 7.0.0-alpha6
== 7.0.0-alpha7
== 7.0.0-alpha8
== 7.0.0-alpha9
High October 25, 2023 10/25/23
>= 1.0.0 < 5.5.6
>= 6.0.0 < 6.3.1
High September 4, 2023 9/4/23
>= 6.0.0 < 6.2.2
< 5.5.5
Critical June 28, 2023 6/28/23
>= 6.0.0 < 6.2.1
< 5.5.2
Medium May 30, 2023 5/30/23
>= 6.0.0 < 6.1.1
< 5.4.4
High February 3, 2023 2/3/23
< 5.4.1
High November 10, 2022 11/10/22
< 4.10.19
>= 5.0.0 < 5.3.2
High November 10, 2022 11/10/22
< 4.10.20
>= 5.0.0 < 5.3.3
Critical November 10, 2022 11/10/22
>= 5.0.0 < 5.3.1
< 4.10.18
High October 24, 2022 10/24/22
>= 5.0.0 < 5.2.8
< 4.10.17
Low September 23, 2022 9/23/22
>= 5.0.0 < 5.2.7
< 4.10.16
Low September 23, 2022 9/23/22
>= 5.0.0 < 5.2.6
< 4.10.15
High September 7, 2022 9/7/22
>= 5.0.0 < 5.2.5
< 4.10.14
High June 30, 2022 6/30/22
< 4.10.13
>= 5.0.0 < 5.2.4
High June 27, 2022 6/27/22
>= 5.0.0 < 5.2.3
< 4.10.12
High June 17, 2022 6/17/22
>= 5.0.0 < 5.2.2
< 4.10.11
High May 4, 2022 5/4/22
>= 5.0.0 < 5.2.1
< 4.10.10
Critical March 12, 2022 3/12/22
< 4.10.7
High September 30, 2021 9/30/21
< 4.10.4
High September 2, 2021 9/2/21
< 4.10.3
Low August 19, 2021 8/19/21
< 4.5.1
High December 30, 2020 12/30/20
< 4.5.0
Low October 22, 2020 10/22/20
<= 4.3.0
High March 4, 2020 3/4/20
< 4.1.0
Medium July 29, 2019 7/29/19
< 3.4.1
Medium July 29, 2019 7/29/19
< 3.6.0
Node.js icon

parse-server

39 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium March 6, 2026 3/6/26
>= 9.0.0 < 9.5.0-alpha.6
< 8.6.7
High March 6, 2026 3/6/26
< 8.6.6
>= 9.0.0 < 9.5.0-alpha.4
Medium March 6, 2026 3/6/26
>= 9.0.0 < 9.5.0-alpha.3
< 8.6.5
High March 5, 2026 3/5/26
>= 9.0.0 < 9.4.1-alpha.3
< 8.6.4
Critical February 25, 2026 2/25/26
>= 9.0.0 < 9.3.1-alpha.4
< 8.6.3
Medium November 10, 2025 11/10/25
< 8.5.0-alpha.5
High November 7, 2025 11/7/25
>= 4.2.0 < 7.5.4
>= 8.0.0 < 8.4.0-alpha.2
Medium July 10, 2025 7/10/25
>= 8.0.0 < 8.2.2
>= 5.3.0 < 7.5.3
Medium March 21, 2025 3/21/25
< 7.5.2
>= 8.0.0 < 8.0.2
Critical July 1, 2024 7/1/24
< 6.5.7
>= 7.0.0 < 7.1.0
Critical March 19, 2024 3/19/24
< 6.5.5
>= 7.0.0-alpha.1 < 7.0.0-alpha.29
Critical March 1, 2024 3/1/24
< 6.5.0
>= 7.0.0-alpha.1 < 7.0.0-alpha.20
High October 25, 2023 10/25/23
>= 1.0.0 < 5.5.6
>= 6.0.0 < 6.3.1
High September 4, 2023 9/4/23
>= 1.0.0 < 5.5.5
>= 6.0.0 < 6.2.2
Critical June 28, 2023 6/28/23
< 5.5.2
>= 6.0.0 < 6.2.1
Medium May 30, 2023 5/30/23
< 5.4.4
>= 6.0.0 < 6.1.1
High February 3, 2023 2/3/23
< 5.4.1
High November 10, 2022 11/10/22
< 4.10.19
>= 5.0.0 < 5.3.2
High November 10, 2022 11/10/22
< 4.10.20
>= 5.0.0 < 5.3.3
Critical November 10, 2022 11/10/22
< 4.10.18
>= 5.0.0 < 5.3.1
High October 24, 2022 10/24/22
< 4.10.17
>= 5.0.0 < 5.2.8
Low September 23, 2022 9/23/22
< 4.10.16
>= 5.0.0 < 5.2.7
Low September 23, 2022 9/23/22
< 4.10.15
>= 5.0.0 < 5.2.6
High September 7, 2022 9/7/22
< 4.10.14
>= 5.0.0 < 5.2.5
High June 30, 2022 6/30/22
< 4.10.13
>= 5.0.0 < 5.2.4
High June 27, 2022 6/27/22
< 4.10.12
>= 5.0.0 < 5.2.3
High June 17, 2022 6/17/22
< 4.10.11
>= 5.0.0 < 5.2.2
High May 4, 2022 5/4/22
< 4.10.10
>= 5.0.0 < 5.2.1
Critical March 12, 2022 3/12/22
< 4.10.7
High September 30, 2021 9/30/21
< 4.10.4
Critical September 7, 2021 9/7/21
>= 4.0.0 < 4.5.2
>= 4.6.0 < 4.10.0
High September 2, 2021 9/2/21
< 4.10.3
Low August 19, 2021 8/19/21
< 4.5.2
High December 30, 2020 12/30/20
< 4.5.0
Low October 22, 2020 10/22/20
< 4.4.0
Medium July 22, 2020 7/22/20
>= 3.5.0 < 4.3.0
High March 4, 2020 3/4/20
< 4.1.0
Medium July 29, 2019 7/29/19
< 3.4.1
Medium July 29, 2019 7/29/19
< 3.6.0

Showing vulnerabilities for 2 products matching "parse--server". Each product has independent pagination.

Frequently Asked Questions

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.