Vulnerability Database

351,770

Total vulnerabilities in the database

Vulnerabilities for products matching "nextgen_gallery"

Found 2 matching products. Filters apply to all results.

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

alex_rabe / nextgen_gallery

90 vulnerabilities found
Title Severity Exploit Date Affected Version
Low April 7, 2010 4/7/10
<= 1.5.1
== 0.33
== 0.34
== 0.35
== 0.36
== 0.37
== 0.39
== 0.40
== 0.41
== 0.42
== 0.43
== 0.50
== 0.51
== 0.52
== 0.60
== 0.61
== 0.62
== 0.63
== 0.64
== 0.70
== 0.71
== 0.72
== 0.73
== 0.74
== 0.80
== 0.81
== 0.82
== 0.83
== 0.90
== 0.91
== 0.92
== 0.93
== 0.94
== 0.95
== 0.96
== 0.97
== 0.98
== 0.99
== 1.0.0
== 1.0.1
== 1.0.2
== 1.1.0
== 1.2.0
== 1.2.1
== 1.3.0
== 1.3.1
== 1.3.2
== 1.3.3
== 1.3.4
== 1.3.5
== 1.3.6
== 1.4.0
== 1.4.1
== 1.4.2
== 1.4.3
== 1.5.0
Low September 8, 2009 9/8/09
<= 0.96
== 0.33
== 0.34
== 0.35
== 0.36
== 0.37
== 0.39
== 0.40
== 0.41
== 0.42
== 0.43
== 0.50
== 0.51
== 0.52
== 0.60
== 0.61
== 0.62
== 0.63
== 0.64
== 0.70
== 0.71
== 0.72
== 0.73
== 0.74
== 0.80
== 0.81
== 0.82
== 0.83
== 0.90
== 0.91
== 0.92
== 0.93
== 0.94
== 0.95

imagely / nextgen_gallery

97 vulnerabilities found
Title Severity Exploit Date Affected Version
Low February 25, 2025 2/25/25
< 3.59.9
Low November 25, 2024 11/25/24
< 3.59.5
Medium August 1, 2024 8/1/24
< 3.59.4
Medium July 13, 2024 7/13/24
< 3.59.3
Low May 17, 2024 5/17/24
< 3.59.1
Medium April 9, 2024 4/9/24
< 3.59.1
Low November 30, 2023 11/30/23
< 3.39
Low October 16, 2023 10/16/23
< 3.39
High October 16, 2023 10/16/23
< 3.39
High October 16, 2023 10/16/23
< 3.39
Low March 1, 2023 3/1/23
< 3.29
High July 7, 2022 7/7/22
< 2.0.77.3
Medium July 7, 2022 7/7/22
< 2.0.77.3
Medium May 5, 2021 5/5/21
< 3.1.11
Medium February 9, 2021 2/9/21
< 3.5.0
High February 9, 2021 2/9/21
< 3.5.0
Critical February 11, 2020 2/11/20
< 1.9.13
High January 30, 2020 1/30/20
== 1.9.11
== 1.9.10
Medium November 26, 2019 11/26/19
< 2.1.10
Medium November 26, 2019 11/26/19
< 2.1.15
High August 27, 2019 8/27/19
< 3.2.10
High August 14, 2019 8/14/19
< 2.1.57
Medium July 13, 2018 7/13/18
< 2.1.57
Low April 30, 2018 4/30/18
<= 2.2.30
Medium March 1, 2018 3/1/18
<= 2.2.46
Low September 12, 2017 9/12/17
== 2.1.15
High September 12, 2017 9/12/17
== 2.1.10
== 2.1.9
== 2.1.7
== 2.1.2
== 2.1.0
== 2.0.79
== 2.0.78.1
== 2.0.78
== 2.0.77
== 2.0.76
== 2.0.74
== 2.0.71
== 2.0.66.33
== 2.0.66.31
== 2.0.66.29
== 2.0.66.27
== 2.0.66.26
== 2.0.66.17
== 2.0.66.16
== 2.0.66
== 2.0.65
== 2.0.63
== 2.0.61
== 2.0.59
== 2.0.58
== 2.0.57
== 2.0.40
== 2.0.33
== 2.0.31
== 2.0.30
== 2.0.27
== 2.0.25
== 2.0.23
== 2.0.21
== 2.0.17
== 2.0.14
== 2.0.11
== 2.0.7
== 2.0
== 1.9.13
== 1.9.12
== 1.9.11
== 1.9.10
== 1.9.8
== 1.9.7
== 1.9.6
== 1.9.5
== 1.9.3
== 1.9.2
== 1.9.1
== 1.9.0
== 1.8.4
== 1.8.3
== 1.8.2
== 1.8.1
== 1.8.0
== 1.7.4
== 1.7.3
== 1.7.2
== 1.7.1
== 1.7.0
== 1.6.2
== 1.6.1
== 1.6.0
== 1.5.5
== 1.5.4
== 1.5.3
== 1.5.2
== 1.5.1
== 1.5.0

Showing vulnerabilities for 2 products matching "nextgen_gallery". 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.