Vulnerabilities for products matching "xoops"
Found 1 matching product.
You can search for specific versions with
/product/xoops/1.2.3
xoops / xoops
44 vulnerabilities found| Title | Severity | Exploit | Date | Affected versions |
|---|---|---|---|---|
|
|
High | February 22, 2026 2/22/26 |
= 2.5.9
|
|
|
|
Critical | August 3, 2023 8/3/23 |
= 2.5.10
|
|
|
|
Medium | September 30, 2019 9/30/19 |
= 2.5.10
|
|
|
|
Medium | September 30, 2019 9/30/19 |
= 2.5.10
|
|
|
|
Medium | August 2, 2017 8/2/17 |
= 2.5.8
|
|
|
|
Medium | August 2, 2017 8/2/17 |
= 2.5.8
|
|
|
|
High | July 12, 2017 7/12/17 |
= 2.5.8.1
|
|
|
|
Medium | April 24, 2017 4/24/17 |
= 2.5.8.1
|
|
|
|
Medium | March 30, 2017 3/30/17 |
= 2.5.7.2
= 2.5.7.3
= 2.5.8.1
|
|
|
|
Medium | November 20, 2014 11/20/14 |
<= 2.5.6
|
|
|
|
Medium | September 11, 2014 9/11/14 |
<= 2.5.4
= 2.5.0
= 2.5.1
= 2.5.2
= 2.5.2-rc
= 2.5.3
|
|
|
|
Medium | November 28, 2011 11/28/11 |
<= 2.5.1.a
= 2.0.2
= 2.0.13.2
= 2.0.14
= 2.0.14-rc1
= 2.0.15
= 2.0.16
= 2.0.17
= 2.0.17.1
= 2.0.17.1-rc
= 2.0.17.1-rc2
= 2.0.18
= 2.0.18-rc
= 2.0.18.1
= 2.0.18.1-rc
= 2.0.18.2
= 2.3.0
= 2.3.1
= 2.3.2a
= 2.3.2b
= 2.3.3
= 2.3.3b
= 2.4.0
= 2.4.1
= 2.4.2
= 2.4.3
= 2.4.4
= 2.4.5
= 2.5.0
= 2.5.1
|
|
|
|
Medium | September 24, 2011 9/24/11 |
= 2.5.0
|
|
|
|
Medium | May 7, 2010 5/7/10 |
<= 2.4.0
= 1.0
= 1.0_rc1
= 1.0_rc3
= 1.0_rc3.0.5
= 1.3.5
= 1.3.6
= 1.3.7
= 1.3.8
= 1.3.9
= 1.3.10
= 2.0.0
= 2.0.0_rc1
= 2.0.0_rc2
= 2.0.0_rc3
= 2.0.1
= 2.0.2
= 2.0.3
= 2.0.4
= 2.0.5.1
= 2.0.5.2
= 2.0.5_rc
= 2.0.6
= 2.0.7
= 2.0.7.1
= 2.0.7.2
= 2.0.7.3
= 2.0.9
= 2.0.9.2
= 2.0.9.3
= 2.0.10
= 2.0.10_rc
= 2.0.11
= 2.0.12
= 2.0.12a
= 2.0.13
= 2.0.13.1
= 2.0.13.2
= 2.0.14
= 2.0.14-rc1
= 2.0.15
= 2.0.16
= 2.0.17
= 2.0.17.1
= 2.0.18
= 2.0.18.1
= 2.3.0
= 2.3.0_alpha_3
= 2.3.0_alpha1
= 2.3.0_alpha2
= 2.3.0_beta
= 2.3.0_rc
= 2.3.0_rc2
= 2.3.0_rc3
= 2.3.1
= 2.3.1_rc
= 2.3.2a
= 2.3.2b
= 2.3.3
= 2.4.0_beta_1
= 2.4.0_beta_2
= 2.4.0_rc
|
|
|
|
High | November 17, 2009 11/17/09 |
<= 2.3.3
= 2.0
= 2.0.1
= 2.0.2
= 2.0.3
= 2.0.4
= 2.0.5
= 2.0.5.1
= 2.0.5.2
= 2.0.6
= 2.0.7
= 2.0.9
= 2.0.9.2
= 2.0.9.3
= 2.0.10
= 2.0.11
= 2.0.12_jp
= 2.0.13.1
= 2.0.13.2
= 2.0.14
= 2.0.16
= 2.0.17.1-rc1
= 2.0.17_1
= 2.0.18
= 2.0.18.1
= 2.2.3
= 2.2.3-rc1
= 2.3.1
= 2.3.2a
|
|
|
|
Medium | August 17, 2009 8/17/09 |
= 2.3.3
|
|
|
|
Medium | July 31, 2009 7/31/09 |
= 2.3.1
|
|
|
|
Medium | July 31, 2009 7/31/09 |
= 2.3.1
= 2.3.2a
|
|
|
|
High | December 19, 2008 12/19/08 |
All versions
|
|
|
|
Medium | July 25, 2008 7/25/08 |
= 2.0.18.1
|
|
|
|
High | July 25, 2008 7/25/08 |
= 2.0.18.1
|
|
|
|
Medium | April 30, 2008 4/30/08 |
= 2.0
|
|
|
|
High | February 6, 2008 2/6/08 |
All versions
|
|
|
|
High | February 6, 2008 2/6/08 |
= 2.0.18
|
|
|
|
Medium | February 6, 2008 2/6/08 |
= 2.0.18
|
|
|
|
Medium | January 8, 2008 1/8/08 |
<= 2.0.17_1
|
|
|
|
High | October 3, 2007 10/3/07 |
<= 2.0.17.1-rc1
|
|
|
|
High | January 19, 2007 1/19/07 |
= 2.0.16
|
|
|
|
Medium | November 8, 2006 11/8/06 |
= 1.0
|
|
|
|
High | August 28, 2006 8/28/06 |
<= 2.0.14
|
|
|
|
Medium | May 22, 2006 5/22/06 |
<= 2.0.13.2
= 2.0
= 2.0.1
= 2.0.2
= 2.0.3
= 2.0.4
= 2.0.5
= 2.0.5.1
= 2.0.5.2
= 2.0.6
= 2.0.7
= 2.0.9
= 2.0.9.2
= 2.0.9.3
= 2.0.10
= 2.0.11
= 2.0.12_jp
= 2.0.13.1
|
|
|
|
Medium | November 18, 2005 11/18/05 |
= 2.2.3
|
|
|
|
Medium | October 27, 2005 10/27/05 |
<= 2.0.12_jp
<= 2.0.13.1
<= 2.2.3_rc1
|
|
|
|
Medium | July 5, 2005 7/5/05 |
= 2.0
= 2.0.1
= 2.0.2
= 2.0.3
= 2.0.4
= 2.0.5
= 2.0.5.1
= 2.0.5.2
= 2.0.6
= 2.0.7
= 2.0.9
= 2.0.9.2
= 2.0.9.3
= 2.0.10
= 2.0.11
|
|
|
|
High | July 5, 2005 7/5/05 |
= 2.0
= 2.0.1
= 2.0.2
= 2.0.3
= 2.0.4
= 2.0.5
= 2.0.5.1
= 2.0.5.2
= 2.0.6
= 2.0.7
= 2.0.9
= 2.0.9.2
= 2.0.9.3
= 2.0.10
= 2.0.11
|
|
|
|
High | May 2, 2005 5/2/05 |
= 1.0_rc1
= 1.0_rc3
= 1.0_rc3.0.5
= 1.3.5
= 1.3.6
= 1.3.7
= 1.3.8
= 1.3.9
= 1.3.10
= 2.0
= 2.0.1
= 2.0.2
= 2.0.3
= 2.0.5
= 2.0.5.1
= 2.0.5.2
= 2.0.9.2
|
|
|
|
Medium | December 31, 2004 12/31/04 |
= 2.0
= 2.0.1
= 2.0.2
= 2.0.3
= 2.0.5
= 2.0.5.1
= 2.0.5.2
|
|
|
|
Medium | December 31, 2003 12/31/03 |
= 1.3.5
= 1.3.6
= 1.3.7
= 1.3.8
= 1.3.9
= 2.0
= 2.0.1
|
|
|
|
Medium | December 31, 2003 12/31/03 |
<= 2.0
|
|
|
|
Medium | December 31, 2002 12/31/02 |
= 1.0_rc3
|
|
|
|
Medium | December 31, 2002 12/31/02 |
= 1.0_rc3
|
|
|
|
High | December 31, 2002 12/31/02 |
= 1.0
|
|
|
|
Medium | May 16, 2002 5/16/02 |
= 1.0_rc1
|
|
|
|
High | May 16, 2002 5/16/02 |
= 1.0_rc1
|
Running xoops 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
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.