How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, 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.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

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.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

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. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

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.

Q: How do we prioritize remediation without burning out the team?

Use a 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 so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

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.

406,586

Total vulnerabilities in the database

Vulnerabilities for products matching "mahara"

Found 2 matching products. Filters apply to all results.

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

mahara / mahara

108 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2024-35203	Medium	August 26, 2025 8/26/25	`< 22.10.6` `>= 23.04.0, < 23.04.6` `>= 24.04.0, < 24.04.1`
CVE-2024-47192	Medium	August 26, 2025 8/26/25	`< 23.04.9` `>= 24.04.0, < 24.04.5`
CVE-2024-39335	Critical	August 26, 2025 8/26/25	`>= 23.04.0, < 23.04.6` `>= 24.04.0, < 24.04.1`
CVE-2025-29992	High	August 26, 2025 8/26/25	`< 24.04.9`
CVE-2024-47853	High	August 26, 2025 8/26/25	`< 23.04.9` `>= 24.04.0, < 24.04.5`
CVE-2024-45753	Medium	August 26, 2025 8/26/25	`< 23.04.9` `>= 24.04.0, < 24.04.5`
CVE-2024-39923	Medium	August 25, 2025 8/25/25	`>= 23.04.0, < 23.04.7` `>= 24.04.0, <= 24.04.2`
CVE-2023-47799	High	August 25, 2025 8/25/25	`< 22.10.4` `>= 23.04.0, < 23.04.4`
CVE-2022-45133	Medium	August 22, 2025 8/22/25	`>= 21.10.0, < 21.10.6` `>= 22.04.0, < 22.04.4` `>= 22.10.0, < 22.10.1`
CVE-2022-45134	Critical	August 22, 2025 8/22/25	`>= 21.10.0, < 21.10.6` `>= 22.04.0, < 22.04.4` `>= 22.10.0, < 22.10.1`
CVE-2022-42707	High	November 6, 2022 11/6/22	`>= 22.04.0, < 22.04.3` `>= 21.10.0, < 21.10.5` `>= 21.04.0, < 21.04.7` `= 22.10.0-rc1`
CVE-2022-44544	Critical	November 6, 2022 11/6/22	`>= 21.04.0, < 21.04.7` `>= 21.10.0, < 21.10.5` `>= 22.04.0, < 22.04.3` `= 22.10.0-rc1`
CVE-2022-33913	High	June 20, 2022 6/20/22	`>= 21.10.0, < 21.10.4` `>= 21.04.0, < 21.04.6` `= 22.04.2`
CVE-2022-28892	High	April 28, 2022 4/28/22	`>= 21.10.0, < 21.10.2` `>= 21.04.0, < 21.04.4` `< 20.10.5` `= 22.04.0-rc1`
CVE-2022-29584	Medium	April 28, 2022 4/28/22	`>= 21.10.0, < 21.10.2` `>= 21.04.0, < 21.04.4` `< 20.10.5` `= 22.04.0-rc1`
CVE-2022-29585	High	April 28, 2022 4/28/22	`>= 21.10.0, < 21.10.2` `>= 21.04.0, < 21.04.4` `< 20.10.5` `= 22.04.0-rc1`
CVE-2022-24111	Medium	February 10, 2022 2/10/22	`>= 21.04.0, < 21.04.3` `= 21.10.0`
CVE-2022-24694	Medium	February 9, 2022 2/9/22	`>= 20.10.0, < 20.10.4` `>= 21.04.0, < 21.04.3` `= 21.10.0` `= 21.10.0-rc1` `= 21.10.0-rc2`
CVE-2021-40848	High	November 3, 2021 11/3/21	`>= 21.04.0, < 21.04.2` `>= 20.10.0, < 20.10.3` `< 20.04.5` `= 21.10.0-rc1` `= 21.10.0-rc2`
CVE-2021-40849	Critical	November 3, 2021 11/3/21	`>= 21.04.0, < 21.04.2` `>= 20.10.0, < 20.10.3` `< 20.04.5` `= 21.10.0-rc1` `= 21.10.0-rc2`
CVE-2021-43264	Low	November 2, 2021 11/2/21	`>= 21.04.0, < 21.04.2` `>= 20.10.0, < 20.10.3` `>= 20.04.0, < 20.04.5`
CVE-2021-43265	Medium	November 2, 2021 11/2/21	`>= 21.04.0, < 21.04.2` `>= 20.10.0, < 20.10.3` `>= 20.04.0, < 20.04.5`
CVE-2021-43266	High	November 2, 2021 11/2/21	`>= 21.04.0, < 21.04.2` `>= 20.10.0, < 20.10.3` `>= 20.04.0, < 20.04.5` `>= 20.10.0, < 20.10.4` `>= 21.04.0, < 21.04.3` `>= 21.10.0, < 21.10.1`
CVE-2021-29349	Medium	March 31, 2021 3/31/21	`= 20.10`
CVE-2020-15907	Medium	August 7, 2020 8/7/20	`>= 19.04, < 19.04.6` `>= 20.04, < 20.04.1` `>= 19.10, < 19.10.4`
CVE-2020-9387	Medium	April 30, 2020 4/30/20	`>= 19.10, < 19.10.3` `>= 19.04, < 19.04.5` `= 20.04-rc1` `= 20.04-rc2`
CVE-2020-9386	Medium	March 9, 2020 3/9/20	`>= 18.10.0, < 18.10.5` `>= 19.04.0, < 19.04.4` `>= 19.10.0, < 19.10.2`
CVE-2020-9282	Medium	March 9, 2020 3/9/20	`>= 18.10.0, < 18.10.5` `>= 19.04.0, < 19.04.4` `>= 19.10.0, < 19.10.2`
CVE-2012-2237	Medium	December 17, 2019 12/17/19	`>= 1.5.0, < 1.5.2` `>= 1.4.0, < 1.4.3`
CVE-2013-1426	Medium	November 7, 2019 11/7/19	`>= 1.6.0, < 1.6.4` `< 1.5.9`
CVE-2019-9708	Medium	May 7, 2019 5/7/19	`>= 18.10.0, < 18.10.1` `>= 18.04.0, < 18.04.4` `>= 17.10.0, < 17.10.8`
CVE-2019-9709	Low	May 7, 2019 5/7/19	`>= 18.10.0, < 18.10.1` `>= 18.04.0, < 18.04.4` `>= 17.10.0, < 17.10.8`
CVE-2018-11195	Low	June 1, 2018 6/1/18	`>= 17.10.0, < 17.10.5` `>= 17.04.0, < 17.04.8` `= 18.04.0`
CVE-2018-11196	Medium	June 1, 2018 6/1/18	`>= 17.10.0, < 17.10.5` `>= 17.04.0, < 17.04.8` `= 18.04.0`
CVE-2018-11565	Medium	May 30, 2018 5/30/18	`>= 17.10.0, < 17.10.5` `>= 17.04.0, < 17.04.8` `= 18.04.0`
CVE-2018-6182	Medium	April 9, 2018 4/9/18	`>= 16.10, < 16.10.9` `>= 17.04, < 17.04.7` `>= 17.10, < 17.10.4`
CVE-2017-17454	Low	February 20, 2018 2/20/18	`>= 16.10.0, < 16.10.7` `>= 17.04.0, < 17.04.5` `>= 17.10.0, < 17.10.2`
CVE-2017-17455	Medium	February 20, 2018 2/20/18	`>= 16.10.0, < 16.10.7` `>= 17.04.0, < 17.04.5` `>= 17.10.0, < 17.10.2`
CVE-2017-1000141	Medium	January 30, 2018 1/30/18	`< 18.10.0`
CVE-2017-1000153	High	November 3, 2017 11/3/17	`= 15.04-rc1` `= 15.04-rc2` `= 15.04.0` `= 15.04.1` `= 15.04.2` `= 15.04.3` `= 15.04.4` `= 15.04.5` `= 15.04.6` `= 15.04.7` `= 15.04.8` `= 15.04.9` `= 16.04-rc1` `= 16.04-rc2` `= 16.04.0` `= 16.04.1` `= 16.04.2` `= 16.04.3` `= 15.10.0` `= 15.10.1` `= 15.10.2` `= 15.10.3` `= 15.10.4` `= 15.10.5`
CVE-2017-1000154	High	November 3, 2017 11/3/17	`= 15.04-rc1` `= 15.04-rc2` `= 15.04.0` `= 15.04.1` `= 15.04.2` `= 15.04.3` `= 15.04.4` `= 15.04.5` `= 15.04.6` `= 15.04.7` `= 16.04-rc1` `= 16.04-rc2` `= 16.04.0` `= 16.04.1` `= 15.10.0` `= 15.10.1` `= 15.10.2` `= 15.10.3`
CVE-2017-1000155	Medium	November 3, 2017 11/3/17	`= 15.04-rc1` `= 15.04-rc2` `= 15.04.0` `= 15.04.1` `= 15.04.2` `= 15.04.3` `= 15.04.4` `= 15.04.5` `= 15.04.6` `= 15.04.7` `= 16.04-rc1` `= 16.04-rc2` `= 16.04.0` `= 16.04.1` `= 15.10.0` `= 15.10.1` `= 15.10.2` `= 15.10.3`
CVE-2017-1000156	Medium	November 3, 2017 11/3/17	`= 15.04-rc1` `= 15.04-rc2` `= 15.04.0` `= 15.04.1` `= 15.04.2` `= 15.04.3` `= 15.04.4` `= 15.04.5` `= 15.04.6` `= 15.04.7` `= 15.04.8` `= 16.04-rc1` `= 16.04-rc2` `= 16.04.0` `= 16.04.1` `= 16.04.2` `= 15.10.0` `= 15.10.1` `= 15.10.2` `= 15.10.3` `= 15.10.4`
CVE-2017-1000157	Low	November 3, 2017 11/3/17	`= 15.04-rc1` `= 15.04-rc2` `= 15.04.0` `= 15.04.1` `= 15.04.2` `= 15.04.3` `= 15.04.4` `= 15.04.5` `= 15.04.6` `= 15.04.7` `= 15.04.8` `= 15.04.9` `= 15.04.10` `= 15.04.11` `= 15.04.12` `= 16.04-rc1` `= 16.04-rc2` `= 16.04.0` `= 16.04.1` `= 16.04.2` `= 16.04.3` `= 16.04.4` `= 16.04.5` `= 16.04.6` `= 16.10-rc1` `= 16.10-rc2` `= 16.10.0` `= 16.10.1` `= 16.10.2` `= 16.10.3` `= 17.04-rc1` `= 17.04-rc2` `= 17.04.0` `= 17.04.1`
CVE-2017-1000131	Medium	November 3, 2017 11/3/17	`= 15.04-rc1` `= 15.04-rc2` `= 15.04.0` `= 15.04.1` `= 15.04.2` `= 15.04.3` `= 15.04.4` `= 15.04.5` `= 15.04.6` `= 15.04.7` `= 16.04-rc1` `= 16.04-rc2` `= 16.04.0` `= 16.04.1` `= 15.10.0` `= 15.10.1` `= 15.10.2` `= 15.10.3`
CVE-2017-1000132	Low	November 3, 2017 11/3/17	`= 1.8-rc1` `= 1.8-rc2` `= 1.8.0` `= 1.8.1` `= 1.8.2` `= 1.8.3` `= 1.8.4` `= 1.8.5` `= 1.8.6` `= 1.9-rc1` `= 1.9.0` `= 1.9.1` `= 1.9.2` `= 1.9.3` `= 1.9.4` `= 1.10-rc1` `= 1.10.0` `= 1.10.1` `= 1.10.2` `= 15.04-rc1` `= 15.04-rc2`
CVE-2017-1000133	Medium	November 3, 2017 11/3/17	`= 15.04-rc1` `= 15.04-rc2` `= 15.04.0` `= 15.04.1` `= 15.04.2` `= 15.04.3` `= 15.04.4` `= 15.04.5` `= 15.04.6` `= 15.04.7` `= 16.04-rc1` `= 16.04-rc2` `= 16.04.0` `= 16.04.1` `= 15.10.0` `= 15.10.1` `= 15.10.2` `= 15.10.3`
CVE-2017-1000134	Medium	November 3, 2017 11/3/17	`= 1.8-rc1` `= 1.8-rc2` `= 1.8.0` `= 1.8.1` `= 1.8.2` `= 1.8.3` `= 1.8.4` `= 1.8.5` `= 1.9-rc1` `= 1.9.0` `= 1.9.1` `= 1.9.2` `= 1.9.3` `= 1.10-rc1` `= 1.10.0` `= 15.04-rc1` `= 15.04-rc2`
CVE-2017-1000135	Medium	November 3, 2017 11/3/17	`= 1.8-rc1` `= 1.8-rc2` `= 1.8.0` `= 1.8.1` `= 1.8.2` `= 1.8.3` `= 1.8.4` `= 1.8.5` `= 1.8.6` `= 1.9-rc1` `= 1.9.0` `= 1.9.1` `= 1.9.2` `= 1.9.3` `= 1.9.4` `= 1.10-rc1` `= 1.10.0` `= 1.10.1` `= 1.10.2` `= 15.04-rc1` `= 15.04-rc2`
CVE-2017-1000136	Medium	November 3, 2017 11/3/17	`= 1.8-rc1` `= 1.8-rc2` `= 1.8.0` `= 1.8.1` `= 1.8.2` `= 1.8.3` `= 1.8.4` `= 1.8.5` `= 1.9-rc1` `= 1.9.0` `= 1.9.1` `= 1.9.2` `= 1.9.3` `= 1.10-rc1` `= 1.10.0` `= 15.04-rc1` `= 15.04-rc2`

catalyst / mahara

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2020-23052	Medium		October 22, 2021 10/22/21	`= 19.10.2`

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

Running mahara 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? →

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

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.