Vulnerability Database

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "invision_power_board"

Found 3 matching products. Filters apply to all results.

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

invision_power_services / invision_power_board

40 vulnerabilities found
Title Severity Exploit Date Affected Version
CVE-2008-6565
Low March 31, 2009 3/31/09
== 2.0_pf1
== 2.2
== 2.1_beta2
== 1.0
== 1.1.2
== 2.0.4
== 2.2.2
== 2.1_rc1
== 2.1.1
== 2.1.6
== 2.1_alpha2
== 2.0_alpha3
== 1.1.1
== 2.1.5_2006-03-08
== 2.1.2
== 2.1.3
== 1.0.3
== 2.0_pdr3
== 2.0
== 2.1_beta5
== 1.3_final
== 2.1.0
== 1.2
== 2.1.5
== 2.0.0
== 2.1.5_2006-04-25
== 1.0.1
== 2.2.1
== 2.0.3
== 2.1_beta4
== 2.1
== 2.1_beta3
== 2.1.4
== 1.3.1_final
== 2.1.7
== 2.0_pf2
== 2.0.2
<= 2.3.1
== 2.0.1
== 2.3
== 1.3
== 2.0.x
== 2.1.x
CVE-2008-4171
High September 22, 2008 9/22/08
== 2.2
== 2.3
CVE-2008-1359
Low March 17, 2008 3/17/08
<= 2.3.4
CVE-2008-0913
Low February 22, 2008 2/22/08
== 2.3.4
CVE-2007-5688
High October 29, 2007 10/29/07
*
CVE-2007-4912
Low September 17, 2007 9/17/07
== 2.2
== 2.2.2
== 2.1.6
== 2.1.5_2006-03-08
== 2.1.5_2006-04-25
== 2.2.1
CVE-2007-4913
High September 17, 2007 9/17/07
== 2.2
== 2.2.2
== 2.1.6
== 2.1.5_2006-03-08
== 2.1.5_2006-04-25
== 2.2.1
<= 2.3.1
CVE-2007-4914
Medium September 17, 2007 9/17/07
== 2.2
== 2.2.2
== 2.1.6
== 2.1.5_2006-03-08
== 2.1.5_2006-04-25
== 2.2.1
<= 2.3.1
CVE-2007-3219
High June 14, 2007 6/14/07
== 2.2
== 2.2.2
== 2.2.1
CVE-2007-2963
Low May 31, 2007 5/31/07
<= 2.2.2
CVE-2007-2349
Medium April 30, 2007 4/30/07
== 2.2
== 2.1
CVE-2006-7071
High March 2, 2007 3/2/07
== 2.1.1
== 2.1.6
== 2.1.2
== 2.1.3
== 2.1.5
== 2.1.4
CVE-2006-7064
High February 24, 2007 2/24/07
== 2.0_pf1
== 2.1_beta2
== 1.0
== 1.1.2
== 2.0.4
== 2.1_rc1
== 2.1.1
== 2.1.6
== 2.1_alpha2
== 2.0_alpha3
== 1.1.1
== 2.1.5_2006-03-08
== 2.1.2
== 2.1.3
== 1.0.3
== 2.0_pdr3
== 2.0
== 2.1_beta5
== 1.3_final
== 2.1.0
== 1.2
== 2.1.5
== 2.0.0
== 2.1.5_2006-04-25
== 1.0.1
== 2.0.3
== 2.1_beta4
== 2.1
== 2.1_beta3
== 2.1.4
== 1.3.1_final
== 2.0_pf2
== 2.0.2
== 2.0.1
== 1.3
== 2.0.x
CVE-2006-5203
Medium October 10, 2006 10/10/06
== 2.0_pf1
== 2.1_beta2
== 1.0
== 1.1.2
== 2.0.4
== 2.1_rc1
== 2.1.1
<= 2.1.7
== 2.1.6
== 2.1_alpha2
== 2.0_alpha3
== 1.1.1
== 2.1.5_2006-03-08
== 2.1.2
== 2.1.3
== 1.0.3
== 2.0_pdr3
== 2.0
== 2.1_beta5
== 1.3_final
== 2.1.0
== 1.2
== 2.1.5
== 2.0.0
== 1.0.1
== 2.0.3
== 2.1_beta4
== 2.1
== 2.1_beta3
== 2.1.4
== 1.3.1_final
== 2.0_pf2
== 2.0.2
== 2.0.1
== 1.3
== 2.0.x
CVE-2006-5204
Low October 10, 2006 10/10/06
== 2.0_pf1
== 2.1_beta2
== 1.0
== 1.1.2
== 2.0.4
== 2.1_rc1
== 2.1.1
<= 2.1.7
== 2.1.6
== 2.1_alpha2
== 2.0_alpha3
== 1.1.1
== 2.1.5_2006-03-08
== 2.1.2
== 2.1.3
== 1.0.3
== 2.0_pdr3
== 2.0
== 2.1_beta5
== 1.3_final
== 2.1.0
== 1.2
== 2.1.5
== 2.0.0
== 1.0.1
== 2.0.3
== 2.1_beta4
== 2.1
== 2.1_beta3
== 2.1.4
== 1.3.1_final
== 2.0_pf2
== 2.0.2
== 2.0.1
== 1.3
== 2.0.x
CVE-2006-4155
High August 16, 2006 8/16/06
<= 2.1.7
CVE-2006-3543
High July 13, 2006 7/13/06
== 2.0_pf1
== 1.0
== 1.1.2
== 2.0.4
== 2.1.6
== 2.1_alpha2
== 2.0_alpha3
== 1.1.1
== 1.0.3
== 2.0_pdr3
== 2.0
== 1.3_final
== 1.2
== 2.1.5
== 1.0.1
== 2.0.3
== 2.1
== 2.1.4
== 1.3.1_final
== 2.0_pf2
== 2.0.2
== 2.0.1
== 1.3
CVE-2006-3197
Low June 23, 2006 6/23/06
== 2.1_beta2
== 2.1_rc1
== 2.1.1
== 2.1.6
== 2.1_alpha2
== 2.1.2
== 2.1.3
== 2.1_beta5
== 2.1.0
== 2.1.5
== 2.1_beta4
== 2.1
== 2.1_beta3
== 2.1.4
CVE-2006-2498
Medium May 20, 2006 5/20/06
== 2.1_beta2
== 2.0.4
== 2.1_rc1
== 2.1.1
== 2.1.6
== 2.1_alpha2
== 2.1.2
== 2.1.3
== 2.1_beta5
== 2.1.0
== 2.1.5
== 2.0.0
== 2.0.3
== 2.1_beta4
== 2.1
== 2.1_beta3
== 2.1.4
== 2.0.2
== 2.0.1
CVE-2006-2204
Medium May 5, 2006 5/5/06
== 2.1_beta2
== 2.0.4
== 2.1_rc1
== 2.1.1
== 2.1_alpha2
== 2.1.2
== 2.1.3
== 2.1_beta5
== 2.1.0
== 2.1.5
== 2.0.0
== 2.0.3
== 2.1_beta4
== 2.1
== 2.1_beta3
== 2.1.4
== 2.0.2
== 2.0.1
== 2.0.x
CVE-2006-2217
High May 5, 2006 5/5/06
== 2.0.4
== 2.1.6
== 2.1_alpha2
== 2.1.5
== 2.0.0
== 2.0.3
== 2.1
== 2.1.4
== 2.0.2
== 2.0.1
CVE-2006-2097
High April 29, 2006 4/29/06
== 2.1_beta2
== 1.0
== 1.1.2
== 2.0.4
== 2.1_rc1
== 2.1.1
== 2.1_alpha2
== 1.1.1
== 2.1.2
== 2.1.3
== 2.1_beta5
== 1.3_final
== 2.1.0
== 1.2
== 2.0.0
== 1.0.1
<= 2.1.4
== 2.0.3
== 2.1_beta4
== 2.1
== 2.1_beta3
== 1.3.1_final
== 2.0.2
== 2.0.1
== 1.3
== 2.0.x
CVE-2006-2059
Medium April 26, 2006 4/26/06
== 2.1.5_2006-03-08
CVE-2006-2060
Medium April 26, 2006 4/26/06
== 2.0.x
== 2.1.x
CVE-2006-2061
Medium April 26, 2006 4/26/06
== 2.1.5_2006-03-08
CVE-2006-1369
Medium March 23, 2006 3/23/06
== 2.1_alpha2
== 2.1.5
== 2.1
CVE-2006-1326
Low March 21, 2006 3/21/06
== 2.0.4
CVE-2006-1287
Medium March 19, 2006 3/19/06
== 2.0.4
== 2.1.4
CVE-2006-1288
High March 19, 2006 3/19/06
== 2.0.4
== 2.1.4
CVE-2006-1267
Medium March 19, 2006 3/19/06
== 2.1.4
CVE-2006-1076
High March 9, 2006 3/9/06
== 2.1.5
CVE-2006-0909
Medium February 28, 2006 2/28/06
== 2.1_beta2
== 2.0.4
== 2.1_rc1
== 2.1.1
== 2.1.2
== 2.1.3
== 2.1_beta5
== 2.1.0
== 2.0.0
== 2.0.3
== 2.1_beta4
== 2.1_beta3
== 2.1.4
== 2.0.2
== 2.0.1
CVE-2006-0910
Medium February 28, 2006 2/28/06
== 2.1_beta2
== 2.0.4
== 2.1_rc1
== 2.1.1
== 2.1.2
== 2.1.3
== 2.1_beta5
== 2.1.0
== 2.0.0
== 2.0.3
== 2.1_beta4
== 2.1_beta3
== 2.1.4
== 2.0.2
== 2.0.1
CVE-2006-0888
Low February 25, 2006 2/25/06
== 2.0.1
CVE-2005-1597
Low May 16, 2005 5/16/05
== 2.0.3
CVE-2005-1598
High May 16, 2005 5/16/05
== 2.0.3
CVE-2005-0477
Low March 30, 2005 3/30/05
== 1.0
== 1.1.2
== 1.1.1
== 1.3_final
== 1.2
== 1.0.1
== 1.3.1_final
== 1.3
CVE-2004-1578
Low December 31, 2004 12/31/04
== 2.0.0
CVE-2004-2279
Low December 31, 2004 12/31/04
== 1.3_final
CVE-2003-1385
Medium December 31, 2003 12/31/03
== 1.1.1

invisionpower / invision_power_board

4 vulnerabilities found
Title Severity Exploit Date Affected Version
CVE-2015-6810
Low September 4, 2015 9/4/15
== 4.0.8.1
== 4.0.11
== 4.0.9.2
== 4.0.1
== 4.0.2
== 4.0.7
== 4.0.4
== 4.0.0
== 4.0.10.2
== 4.0.12
== 4.0.6.1
== 4.0.3
== 4.0.8
== 4.0.5.1
CVE-2014-9239
High December 3, 2014 12/3/14
== 3.4.7
CVE-2012-5692
High October 31, 2012 10/31/12
== 3.1.4
== 3.1.3
== 3.2.1
== 3.1.0
== 3.1.1
== 3.2.2
== 3.2.0
CVE-2006-0633
Medium February 10, 2006 2/10/06
== 2.1.4

invisioncommunity / invision_power_board

19 vulnerabilities found
Title Severity Exploit Date Affected Version
CVE-2021-39249
Medium August 17, 2021 8/17/21
< 4.6.5.1
CVE-2021-39250
Medium August 17, 2021 8/17/21
< 4.6.5.1
CVE-2009-5159
Medium March 13, 2020 3/13/20
>= 2.0 <= 3.0.4
CVE-2013-3725
Critical February 12, 2020 2/12/20
< 4.0.0
CVE-2012-2226
Critical January 9, 2020 1/9/20
< 3.3.1
CVE-2019-8278
Low March 2, 2019 3/2/19
>= 3.3.1 <= 3.4.8
CVE-2014-4928
Medium March 20, 2018 3/20/18
< 3.4.6
CVE-2017-8897
Low May 11, 2017 5/11/17
<= 4.1.19.2
CVE-2017-8898
High May 11, 2017 5/11/17
<= 4.1.19.2
CVE-2017-8899
Medium May 11, 2017 5/11/17
<= 4.1.19.2
CVE-2016-2564
Low April 23, 2017 4/23/17
<= 4.1.8.1
CVE-2016-6174
Medium July 12, 2016 7/12/16
<= 4.1.12.3
CVE-2015-6812
High September 4, 2015 9/4/15
<= 4.0.11
CVE-2014-9239
High December 3, 2014 12/3/14
== 3.3.0-alpha1
== 3.3.0-alpha2
== 3.3.0-beta1
== 3.3.0-beta2
== 3.3.0-beta3
== 3.3.0
== 3.3.0-beta4
== 3.3.1
== 3.3.2
== 3.3.3
== 3.3.4
== 3.4.0-alpha1
== 3.4.0-beta1
== 3.4.0-beta2
== 3.4.0-beta3
== 3.4.0-beta4
== 3.4.0-beta5
== 3.4.0
== 3.4.1
== 3.4.2
== 3.4.3
== 3.4.4
== 3.4.5
== 3.4.6
CVE-2014-5106
Low July 28, 2014 7/28/14
== 3.4.0-alpha1
== 3.4.0-beta1
== 3.4.0-beta2
== 3.4.0-beta3
== 3.4.0-beta4
== 3.4.0-beta5
== 3.4.0
== 3.4.1
== 3.4.2
== 3.4.3
== 3.4.4
== 3.4.5
== 3.4.6
CVE-2014-3149
Low July 3, 2014 7/3/14
== 3.3.0-alpha1
== 3.3.0-alpha2
== 3.3.0-beta1
== 3.3.0-beta2
== 3.3.0-beta3
== 3.3.0
== 3.3.0-beta4
== 3.3.1
== 3.3.2
== 3.3.3
== 3.3.4
== 3.4.0-alpha1
== 3.4.0-beta1
== 3.4.0-beta2
== 3.4.0-beta3
== 3.4.0-beta4
== 3.4.0-beta5
== 3.4.0
== 3.4.1
== 3.4.2
== 3.4.3
== 3.4.4
== 3.4.5
== 3.4.6
CVE-2012-5692
High October 31, 2012 10/31/12
== 3.1.2
== 3.3.0
CVE-2010-3424
Low September 16, 2010 9/16/10
== 3.1.2
CVE-2009-3974
High November 18, 2009 11/18/09
== 3.0.0
== 3.0.1
== 3.0.2

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