Vulnerability Database

413,619

Total vulnerabilities in the database

Vulnerabilities for products matching "parse_server"

Found 3 matching products. Filters apply to all results.

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

parseplatform / parse-server

137 vulnerabilities found
Title Severity Exploit Date Affected versions
Medium March 9, 2026 3/9/26
< 8.6.8
>= 9.0.0, < 9.5.0
= 9.5.0-alpha1
= 9.5.0-alpha2
= 9.5.0-alpha3
= 9.5.0-alpha4
= 9.5.0-alpha5
= 9.5.0-alpha6
= 9.5.0-alpha7
Medium March 6, 2026 3/6/26
< 8.6.7
>= 9.0.0, < 9.5.0
= 9.5.0-alpha1
= 9.5.0-alpha2
= 9.5.0-alpha3
= 9.5.0-alpha4
= 9.5.0-alpha5
High March 6, 2026 3/6/26
< 8.6.6
>= 9.0.0, <= 9.4.1
= 9.5.0-alpha1
= 9.5.0-alpha2
= 9.5.0-alpha3
Medium March 6, 2026 3/6/26
< 8.6.5
>= 9.0.0, <= 9.4.1
= 9.5.0-alpha1
= 9.5.0-alpha2
High March 5, 2026 3/5/26
< 8.6.4
>= 9.0.0, <= 9.4.0
= 9.4.1-alpha1
= 9.4.1-alpha2
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
High 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 24, 2023 10/24/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 30, 2023 6/30/23
>= 6.0.0, < 6.2.1
< 5.5.2
Medium May 31, 2023 5/31/23
>= 6.0.0, < 6.1.1
< 5.4.4
High January 31, 2023 1/31/23
< 5.4.1
High November 10, 2022 11/10/22
< 4.10.20
>= 5.0.0, < 5.3.3
High November 9, 2022 11/9/22
< 4.10.19
>= 5.0.0, < 5.3.2
Critical November 8, 2022 11/8/22
>= 5.0.0, < 5.3.1
< 4.10.18
High October 18, 2022 10/18/22
>= 5.0.0, < 5.2.8
< 4.10.17
Low September 21, 2022 9/21/22
>= 5.0.0, < 5.2.7
< 4.10.16
Medium September 21, 2022 9/21/22
>= 5.0.0, < 5.2.6
< 4.10.15
High September 16, 2022 9/16/22
>= 5.0.0, < 5.2.5
< 4.10.14
High July 6, 2022 7/6/22
< 4.10.13
>= 5.0.0, < 5.2.4
High June 20, 2022 6/20/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 11, 2022 3/11/22
< 4.10.7
High September 30, 2021 9/30/21
< 4.10.4
High September 2, 2021 9/2/21
< 4.10.3
Medium August 23, 2021 8/23/21
< 4.5.1
Low December 28, 2020 12/28/20
< 4.5.0
Medium October 27, 2020 10/27/20
<= 4.3.0
High March 4, 2020 3/4/20
< 4.1.0
Medium July 11, 2019 7/11/19
< 3.6.0
High June 13, 2019 6/13/19
< 3.4.1
Node.js icon

parse-server

119 vulnerabilities found
Title Severity Exploit Date Affected versions
High October 18, 2022 10/18/22
< 4.10.17
>= 5.0.0, < 5.2.8
Low September 21, 2022 9/21/22
< 4.10.16
>= 5.0.0, < 5.2.7
Medium September 21, 2022 9/21/22
< 4.10.15
>= 5.0.0, < 5.2.6
High September 16, 2022 9/16/22
< 4.10.14
>= 5.0.0, < 5.2.5
High July 6, 2022 7/6/22
< 4.10.13
>= 5.0.0, < 5.2.4
High June 20, 2022 6/20/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 11, 2022 3/11/22
< 4.10.7
High September 30, 2021 9/30/21
< 4.10.4
High 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
Medium August 23, 2021 8/23/21
< 4.5.2
Low December 28, 2020 12/28/20
< 4.5.0
Medium October 27, 2020 10/27/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 11, 2019 7/11/19
< 3.6.0
High June 13, 2019 6/13/19
< 3.4.1

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

Running Parse Server on internet-facing hosts?

Knowing a product's CVEs is half the job; the other half is knowing every place it is exposed. Attack surface management continuously maps your external assets and the software they run.

What is attack surface management? →

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.