Vulnerability Database

417,502

Total vulnerabilities in the database

Vulnerabilities for products matching "mybb"

Found 2 matching products. Filters apply to all results.

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

mybb / mybb

146 vulnerabilities found
Title Severity Exploit Date Affected versions
Medium April 11, 2019 4/11/19
>= 1.8.0, < 1.8.20
Medium March 29, 2019 3/29/19
< 1.8.20
Low September 17, 2018 9/17/18
< 1.8.19
Medium August 28, 2018 8/28/18
= 1.8.17
Medium June 26, 2018 6/26/18
< 1.8.15
Medium June 26, 2018 6/26/18
< 1.8.15
Medium May 13, 2018 5/13/18
= 1.8.15
Medium February 21, 2018 2/21/18
= 1.8.14
Low February 8, 2018 2/8/18
= 1.8.14
High November 10, 2017 11/10/17
<= 1.8.12
Low November 10, 2017 11/10/17
<= 1.8.12
Medium April 24, 2017 4/24/17
<= 1.8.10
Medium April 24, 2017 4/24/17
<= 1.8.10
Medium April 6, 2017 4/6/17
<= 1.8.10
High January 31, 2017 1/31/17
<= 1.8.6
High January 31, 2017 1/31/17
<= 1.8.6
Medium January 31, 2017 1/31/17
<= 1.8.6
Medium January 31, 2017 1/31/17
<= 1.8.6
Medium January 31, 2017 1/31/17
<= 1.8.6
Medium January 31, 2017 1/31/17
<= 1.8.6
Medium January 31, 2017 1/31/17
<= 1.8.6
Medium January 31, 2017 1/31/17
<= 1.8.6
Medium January 31, 2017 1/31/17
<= 1.8.6
Medium January 31, 2017 1/31/17
<= 1.8.6
High January 31, 2017 1/31/17
<= 1.8.6
Medium January 31, 2017 1/31/17
<= 1.8.6
Medium January 31, 2017 1/31/17
<= 1.8.6
Medium January 31, 2017 1/31/17
<= 1.8.7
High January 31, 2017 1/31/17
<= 1.8.7
Medium January 31, 2017 1/31/17
<= 1.8.7
Medium January 31, 2017 1/31/17
<= 1.8.7
Medium January 31, 2017 1/31/17
<= 1.8.7
High January 31, 2017 1/31/17
<= 1.8.7
Medium January 31, 2017 1/31/17
<= 1.8.7
High January 31, 2017 1/31/17
<= 1.6.17
= 1.8.0
= 1.8.1
= 1.8.2
= 1.8.3
= 1.8.4
= 1.8.5
High January 31, 2017 1/31/17
<= 1.6.17
= 1.8.0
= 1.8.1
= 1.8.2
= 1.8.3
= 1.8.4
= 1.8.5
Medium January 31, 2017 1/31/17
<= 1.6.17
= 1.8.0
= 1.8.1
= 1.8.2
= 1.8.3
= 1.8.4
= 1.8.5
Medium January 31, 2017 1/31/17
<= 1.6.17
= 1.8.0
= 1.8.1
= 1.8.2
= 1.8.3
= 1.8.4
= 1.8.5
Medium January 31, 2017 1/31/17
<= 1.6.17
= 1.8.0
= 1.8.1
= 1.8.2
= 1.8.3
= 1.8.4
= 1.8.5
Medium September 3, 2015 9/3/15
<= 1.8.4
High March 29, 2015 3/29/15
<= 1.8.3
High March 19, 2015 3/19/15
<= 1.8.3
Medium March 18, 2015 3/18/15
<= 1.8.3
Medium March 18, 2015 3/18/15
<= 1.8.3
Medium March 18, 2015 3/18/15
<= 1.8.3
Medium March 18, 2015 3/18/15
<= 1.8.3
Low March 18, 2015 3/18/15
<= 1.8.3
Medium December 3, 2014 12/3/14
= 1.8.0
= 1.8.1
High December 3, 2014 12/3/14
= 1.8.0
= 1.8.1
Medium August 14, 2014 8/14/14
<= 1.6.14
= 1.6.0
= 1.6.1
= 1.6.2
= 1.6.3
= 1.6.4
= 1.6.5
= 1.6.6
= 1.6.7
= 1.6.8
= 1.6.9
= 1.6.10
= 1.6.11
= 1.6.12
= 1.6.13

Showing vulnerabilities for 2 products matching "mybb". Each product has independent pagination.

Running mybb 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.