Vulnerability Database

325,773

Total vulnerabilities in the database

Vulnerabilities for products matching "geeklog"

Found 2 matching products. Filters apply to all results.

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

geeklog / geeklog

31 vulnerabilities found
Title Severity Exploit Date Affected Version
CVE-2023-46059
Low October 24, 2023 10/24/23
== 2.2.2
CVE-2023-46058
Low October 24, 2023 10/24/23
== 2.2.2
CVE-2023-37787
Low July 13, 2023 7/13/23
== 2.2.2
CVE-2023-37786
Low July 13, 2023 7/13/23
== 2.2.2
CVE-2013-1470
Low February 5, 2014 2/5/14
== 2.0.0-rc2
== 1.8.2
== 2.0.0-rc1
CVE-2011-4942
Low September 9, 2012 9/9/12
== 1.3.5
== 1.3.8
== 1.3.6
== 1.3.7
== 1.35
== 1.5.0
== 1.3.10
== 1.5.1
== 1.3
== 1.4.0
<= 1.7.1
== 1.3.9
== 1.5.2
== 1.3.11
CVE-2011-5159
Low September 9, 2012 9/9/12
== 1.3.5
== 1.3.8
== 1.3.6
== 1.3.7
== 1.35
== 1.5.0
== 1.3.10
== 1.5.1
== 1.3
== 1.4.0
<= 1.7.1
== 1.3.9
== 1.5.2
== 1.3.11
CVE-2011-4647
Low November 30, 2011 11/30/11
== 1.8.0
CVE-2010-4933
High October 9, 2011 10/9/11
== 1.3.8
CVE-2009-3021
Low August 31, 2009 8/31/09
== 1.5.0
== 1.5.1
== 1.5.2
CVE-2007-2793
High May 22, 2007 5/22/07
== 2.x
CVE-2007-0810
High February 7, 2007 2/7/07
== 2
CVE-2006-6225
Medium December 2, 2006 12/2/06
== 1.4.0_sr1
== 1.4.0_beta1
== 1.4.0_sr2
== 1.4.0_sr3
== 1.4.0
== 1.4.0_sr4
CVE-2006-3756
Low July 21, 2006 7/21/06
== 1.4.0
== 1.3.11
== 1.3.11-sr1
== 1.3.11-sr2
== 1.3.11-sr3
== 1.3.11-sr4
== 1.3.11-sr5
== 1.3.11-sr6
== 1.4.0-sr1
== 1.4.0-sr2
== 1.4.0-sr3
== 1.4.0-sr4
CVE-2006-3362
Medium July 6, 2006 7/6/06
== 1.4.0_sr1
== 1.4.0_sr2
== 1.4.0_sr3
== 1.4.0
CVE-2006-2698
High May 31, 2006 5/31/06
== 1.3.5
== 1.3.10_rc3
== 1.4.0_sr1
== 1.3.8
== 1.3.9_sr2
== 1.3.10_rc2
== 1.3.6
== 1.4.0_beta1
== 1.3.9_sr4
== 1.3.11_sr3
== 1.3.9_rc3
== 1.3.7_sr2
== 1.3.11_sr2
== 1.3.7_sr5
== 1.3.8_1_sr5
== 1.3.7
== 1.35
== 1.3.9_rc1
== 1.3.10
== 1.3.8_1_sr2
== 1.3.8_1_sr6
== 1.3.8_1_sr1
== 1.3.8_1_sr3
== 1.3.11_rc1
== 1.3
== 1.3.7_sr3
== 1.3.8_1_sr4
== 1.4.0
== 1.3.9_sr1
== 1.3.11_sr1
== 1.3.9
== 1.3.7_sr1
== 1.3.5_sr1
== 1.3.9_rc2
== 1.3.9_sr3
== 1.3.11_sr4
== 1.3.11
== 1.3.8_1
== 1.3.10_rc1
== 1.3.7_sr4
<= 1.4.0_sr2
CVE-2006-2699
Medium May 31, 2006 5/31/06
== 1.3.5
== 1.3.10_rc3
== 1.4.0_sr1
== 1.3.8
== 1.3.9_sr2
== 1.3.10_rc2
== 1.3.6
== 1.4.0_beta1
== 1.3.9_sr4
== 1.3.11_sr3
== 1.3.9_rc3
== 1.3.7_sr2
== 1.3.11_sr2
== 1.3.7_sr5
== 1.3.8_1_sr5
== 1.3.7
== 1.35
== 1.3.9_rc1
== 1.3.10
== 1.3.8_1_sr2
== 1.3.8_1_sr6
== 1.3.8_1_sr1
== 1.4.0_sr2
== 1.3.8_1_sr3
== 1.3.11_rc1
== 1.3
== 1.3.7_sr3
== 1.3.8_1_sr4
== 1.4.0
== 1.3.9_sr1
== 1.3.11_sr1
== 1.3.9
== 1.3.7_sr1
== 1.3.5_sr1
== 1.3.9_rc2
== 1.3.9_sr3
== 1.3.11_sr4
== 1.3.11
== 1.3.8_1
== 1.3.10_rc1
== 1.3.7_sr4
CVE-2006-2700
Medium May 31, 2006 5/31/06
== 1.3.5
== 1.3.10_rc3
== 1.4.0_sr1
== 1.3.8
== 1.3.9_sr2
== 1.3.10_rc2
== 1.3.6
== 1.4.0_beta1
== 1.3.9_sr4
== 1.3.11_sr3
== 1.3.9_rc3
== 1.3.7_sr2
== 1.3.11_sr2
== 1.3.7_sr5
== 1.3.8_1_sr5
== 1.3.7
== 1.35
== 1.3.9_rc1
== 1.3.10
== 1.3.8_1_sr2
== 1.3.8_1_sr6
== 1.3.8_1_sr1
== 1.3.8_1_sr3
== 1.3.11_rc1
== 1.3
== 1.3.7_sr3
== 1.3.8_1_sr4
== 1.4.0
== 1.3.9_sr1
== 1.3.11_sr1
== 1.3.9
== 1.3.7_sr1
== 1.3.5_sr1
== 1.3.9_rc2
== 1.3.9_sr3
== 1.3.11_sr4
== 1.3.11
== 1.3.8_1
== 1.3.10_rc1
== 1.3.7_sr4
<= 1.4.0_sr2
CVE-2006-2701
High May 31, 2006 5/31/06
== 1.3.5
== 1.3.10_rc3
== 1.4.0_sr1
== 1.3.8
== 1.3.9_sr2
== 1.3.10_rc2
== 1.3.6
== 1.4.0_beta1
== 1.3.9_sr4
== 1.3.11_sr3
== 1.3.9_rc3
== 1.3.7_sr2
== 1.3.11_sr2
== 1.3.7_sr5
== 1.3.8_1_sr5
== 1.3.7
== 1.35
== 1.3.9_rc1
== 1.3.10
== 1.3.8_1_sr2
== 1.3.8_1_sr6
== 1.3.8_1_sr1
== 1.3.8_1_sr3
== 1.3.11_rc1
== 1.3
== 1.3.7_sr3
== 1.3.8_1_sr4
== 1.4.0
== 1.3.9_sr1
== 1.3.11_sr1
== 1.3.9
== 1.3.7_sr1
== 1.3.5_sr1
== 1.3.9_rc2
== 1.3.9_sr3
== 1.3.11_sr4
== 1.3.11
== 1.3.8_1
== 1.3.10_rc1
== 1.3.7_sr4
<= 1.4.0_sr2
CVE-2006-1069
High March 7, 2006 3/7/06
== 1.4.0_sr1
== 1.3.9_sr2
== 1.3.9_sr4
== 1.3.11_sr3
== 1.3.11_sr2
== 1.4.0
== 1.3.9_sr1
== 1.3.11_sr1
== 1.3.9
== 1.3.9_sr3
== 1.3.11_sr4
== 1.3.11
CVE-2006-0823
High February 21, 2006 2/21/06
== 1.3.11_sr3
== 1.3.11_sr2
== 1.4.0
== 1.3.11_sr1
== 1.3.11
CVE-2006-0824
High February 21, 2006 2/21/06
== 1.3.11_sr3
== 1.3.11_sr2
== 1.4.0
== 1.3.11_sr1
== 1.3.11
CVE-2005-4725
High December 31, 2005 12/31/05
== 1.3.10_rc3
== 1.3.9_sr2
== 1.3.10_rc2
== 1.3.9_rc3
== 1.3.11_sr2
== 1.3.9_rc1
== 1.3.10
== 1.3.8_1_sr3
== 1.3.11_rc1
== 1.3.8_1_sr4
== 1.3.9_sr1
== 1.3.11_sr1
== 1.3.9
== 1.3.9_rc2
== 1.3.11
== 1.3.10_rc1
CVE-2005-4026
Medium December 5, 2005 12/5/05
== 1.4.0-beta1
>= 1.3.0 <= 1.3.11
== 1.3.11-rc1
== 1.3.11-sr1
== 1.3.11-sr2
CVE-2005-2152
High July 6, 2005 7/6/05
== 1.3.8
== 1.3.9_sr2
== 1.3.6
== 1.3.7_sr2
== 1.3.7_sr5
== 1.3.8_1_sr5
== 1.3.7
== 1.3.10
== 1.3.8_1_sr2
== 1.3.8_1_sr6
== 1.3.8_1_sr1
== 1.3.8_1_sr3
== 1.3.7_sr3
== 1.3.8_1_sr4
== 1.3.9_sr1
== 1.3.7_sr1
== 1.3.9_sr3
== 1.3.8_1
== 1.3.7_sr4
CVE-2003-1347
Low December 31, 2003 12/31/03
== 1.3.7
CVE-2002-1917
Medium December 31, 2002 12/31/02
== 1.35
== 1.3.5_sr1
CVE-2002-0962
High October 4, 2002 10/4/02
<= 1.3.5
CVE-2002-0963
Medium October 4, 2002 10/4/02
<= 1.3.5
CVE-2002-0096
High March 25, 2002 3/25/02
== 1.3
CVE-2002-0097
High March 25, 2002 3/25/02
== 1.3

geeklog_project / geeklog

1 vulnerabilities found
Title Severity Exploit Date Affected Version
CVE-2016-4849
Low April 20, 2017 4/20/17
== 2.1.1

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