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.

327,059

Total vulnerabilities in the database

Vulnerabilities for products matching "dokuwiki"

Found 3 matching products. Filters apply to all results.

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

andreas_gohr / dokuwiki

14 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2012-2128	Medium	August 27, 2012 8/27/12	== 2012-01-25
CVE-2012-2129	Low	August 27, 2012 8/27/12	== 2012-01-25
CVE-2012-0283	Low	July 13, 2012 7/13/12	== 2006-11-06 == 2006-03-05 == 2011-05-25 == 2011-05-25c == 2005-09-22 == 2005-07-01 == 2010-11-07a == 2009-12-25c == 2009-02-14b == 2012-01-25 == 2005-09-19 == 2011-05-25a == 2006-03-09 == 2008-05-05 <= 2012-01-25a == 2007-06-26 == 2007-07-13
CVE-2006-6965	Low	January 29, 2007 1/29/07	== release_2006-03-09 == release_2006-03-09e
CVE-2006-5098	Medium	September 29, 2006 9/29/06	== release_2006-03-09 == release_2006-03-09e == release_2006-03-05
CVE-2006-5099	High	September 29, 2006 9/29/06	== release_2006-03-09 == release_2006-03-09e == release_2006-03-05
CVE-2006-4674	High	September 11, 2006 9/11/06	== release_2004-07-07 == release_2004-08-08 == release_2005-02-06 == release_2005-01-16a == release_2004-09-12 == release_2005-05-07 == release_2004-07-25 == release_2004-08-22 == release_2004-09-25 == release_2005-02-18 <= release_2006-03-09 == release_2005-09-22 == release_2004-11-10 == release_2005-01-15 == release_2005-01-14 == release_2004-07-04 == release_2005-07-01 == release_2004-07-21 == release_2006-03-05 == release_2005-07-13 == release_2004-09-30 == release_2004-08-15a == release_2004-10-19 == release_2005-09-19 == release_2004-11-01 == release_2004-07-12 == release_2004-11-02
CVE-2006-4675	High	September 11, 2006 9/11/06	== release_2004-07-07 == release_2004-08-08 == release_2005-02-06 == release_2005-01-16a == release_2004-09-12 == release_2005-05-07 == release_2004-07-25 == release_2004-08-22 == release_2004-09-25 == release_2005-02-18 <= release_2006-03-09 == release_2005-09-22 == release_2004-11-10 == release_2005-01-15 == release_2005-01-14 == release_2004-07-04 == release_2005-07-01 == release_2004-07-21 == release_2006-03-05 == release_2005-07-13 == release_2004-09-30 == release_2004-08-15a == release_2004-10-19 == release_2005-09-19 == release_2004-11-01 == release_2004-07-12 == release_2004-11-02
CVE-2006-4679	Medium	September 11, 2006 9/11/06	== release_2004-07-07 == release_2004-08-08 == release_2005-02-06 == release_2005-01-16a == release_2004-09-12 == release_2005-05-07 == release_2004-07-25 == release_2004-08-22 == release_2004-09-25 == release_2005-02-18 <= release_2006-03-09 == release_2005-09-22 == release_2004-11-10 == release_2005-01-15 == release_2005-01-14 == release_2004-07-04 == release_2005-07-01 == release_2004-07-21 == release_2006-03-05 == release_2005-07-13 == release_2004-09-30 == release_2004-08-15a == release_2004-10-19 == release_2005-09-19 == release_2004-11-01 == release_2004-07-12 == release_2004-11-02
CVE-2006-2945	Low	June 12, 2006 6/12/06	== release_2004-07-07 == release_2004-08-08 == release_2005-02-06 == release_2005-01-16a == release_2004-09-12 == release_2005-05-07 == release_2004-07-25 == release_2004-08-22 == release_2004-09-25 == release_2005-02-18 <= release_2006-03-09 == release_2005-09-22 == release_2004-11-10 == release_2005-01-15 == release_2005-01-14 == release_2004-07-04 == release_2005-07-01 == release_2004-07-21 == release_2006-03-05 == release_2005-07-13 == release_2004-09-30 == release_2004-08-15a == release_2004-10-19 == release_2005-09-19 == release_2004-11-01 == release_2004-07-12 == release_2004-11-02
CVE-2006-2878	High	June 7, 2006 6/7/06	== release_2004-07-07 == release_2004-08-08 == release_2005-02-06 == release_2005-01-16a == release_2004-09-12 == release_2005-05-07 == release_2004-07-25 == release_2004-08-22 == release_2004-09-25 == release_2005-02-18 == release_2005-09-22 == release_2004-11-10 == release_2005-01-15 <= release_2006-06-04 == release_2005-01-14 == release_2004-07-04 == release_2005-07-01 == release_2004-07-21 == release_2006-03-05 == release_2005-07-13 == release_2004-09-30 == release_2004-08-15a == release_2004-10-19 == release_2005-09-19 == release_2004-11-01 == release_2004-07-12 == release_2004-11-02
CVE-2006-1165	Low	March 12, 2006 3/12/06	== release_2004-07-07 == release_2004-08-08 == release_2005-02-06 == release_2005-01-16a == release_2004-09-12 == release_2005-05-07 == release_2004-07-25 == release_2004-08-22 == release_2004-09-25 == release_2005-02-18 == release_2005-09-22 == release_2004-11-10 == release_2005-01-15 == release_2005-01-14 == release_2004-07-04 == release_2005-07-01 == release_2004-07-21 == release_2006-03-05 == release_2005-07-13 == release_2004-09-30 == release_2004-08-15a == release_2004-10-19 == release_2005-09-19 == release_2004-11-01 == release_2004-07-12 == release_2004-11-02
CVE-2004-2559	High	December 31, 2004 12/31/04	== release_2004-07-07 == release_2004-08-08 == release_2004-09-12 == release_2004-07-25 == release_2004-08-22 == release_2004-09-25 == release_2004-07-04 == release_2004-07-21 == release_2004-09-30 == release_2004-08-15a == release_2004-07-12
CVE-2004-2560	High	December 31, 2004 12/31/04	== release_2004-07-07 == release_2004-08-08 == release_2004-09-12 == release_2004-07-25 == release_2004-08-22 == release_2004-09-25 == release_2004-07-04 == release_2004-07-21 == release_2004-09-30 == release_2004-08-15a == release_2004-07-12

wiki / dokuwiki

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2007-3930	Low		July 21, 2007 7/21/07	<= 2007-06-26

dokuwiki / dokuwiki

23 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2019-25338	Medium	February 12, 2026 2/12/26	== 2018-04-22b
CVE-2023-34408	Medium	June 5, 2023 6/5/23	< 2023-04-04a
CVE-2022-3123	Medium	September 5, 2022 9/5/22	< 2022-07-31a
CVE-2022-28919	Medium	May 12, 2022 5/12/22	== 2020-07-29
CVE-2018-15474	Medium	September 7, 2018 9/7/18	<= 2018-04-22a
CVE-2017-18123	High	February 3, 2018 2/3/18	<= 2017-02-19e
CVE-2017-12979	Low	August 21, 2017 8/21/17	<= 2017-02-19c
CVE-2017-12980	Low	August 21, 2017 8/21/17	<= 2017-02-19c
CVE-2017-12583	Low	August 6, 2017 8/6/17	<= 2017-02-19b
CVE-2016-7965	Low	October 31, 2016 10/31/16	<= 2016-06-26a
CVE-2016-7964	Low	October 31, 2016 10/31/16	== 2016-06-26a
CVE-2015-2172	Medium	March 30, 2015 3/30/15	>= 2014-09-29 < 2014-09-29c >= 2014-05-05 < 2014-05-05d
CVE-2014-9253	Low	December 17, 2014 12/17/14	<= 2014-05-05c
CVE-2014-8761	Medium	October 22, 2014 10/22/14	<= 2013-12-08
CVE-2014-8762	Medium	October 22, 2014 10/22/14	<= 2013-12-08
CVE-2014-8763	Medium	October 22, 2014 10/22/14	<= 2014-05-05a
CVE-2014-8764	Medium	October 22, 2014 10/22/14	<= 2013-12-08
CVE-2011-3727	Medium	September 23, 2011 9/23/11	== 2009-12-25c
CVE-2011-2510	Low	July 14, 2011 7/14/11	== 2008-05-05 == 2006-03-05 == 2009-02-14b == 2005-09-19 == 2005-07-13 == 2009-12-25c == 2005-09-22 == 2006-03-09 <= 2010-11-07a == 2006-11-06 == 2007-06-26 == 2005-07-01
CVE-2010-0287	Medium	February 15, 2010 2/15/10	<= release_2009-02-14 == 2006-03-05 == 2005-09-19 == 2005-07-13 == 2005-09-22 == 2006-03-09 == 2005-07-01 == 2004-07-04 == 2004-07-07 == 2004-07-12 == 2004-07-21 == 2004-07-25 == 2004-08-08 == 2004-08-15a == 2004-08-22 == 2004-09-12 == 2004-09-25 == 2004-09-30 == 2004-11-01 == 2004-11-02 == 2004-11-10 == 2005-01-14 == 2005-01-15 == 2005-01-16a == 2005-02-06 == 2005-02-18 == 2005-05-07 == 2006-03-09e == 2006-06-04
CVE-2010-0288	High	February 15, 2010 2/15/10	<= release_2009-02-14 == 2006-03-05 == 2005-09-19 == 2005-07-13 == 2005-09-22 == 2006-03-09 == 2005-07-01 == 2004-07-04 == 2004-07-07 == 2004-07-12 == 2004-07-21 == 2004-07-25 == 2004-08-08 == 2004-08-15a == 2004-08-22 == 2004-09-12 == 2004-09-25 == 2004-09-30 == 2004-11-01 == 2004-11-02 == 2004-11-10 == 2005-01-14 == 2005-01-15 == 2005-01-16a == 2005-02-06 == 2005-02-18 == 2005-05-07 == 2006-03-09e == 2006-06-04
CVE-2010-0289	Medium	February 15, 2010 2/15/10	<= release_2009-02-14 == 2006-03-05 == 2005-09-19 == 2005-07-13 == 2005-09-22 == 2006-03-09 == 2005-07-01 == 2004-07-04 == 2004-07-07 == 2004-07-12 == 2004-07-21 == 2004-07-25 == 2004-08-08 == 2004-08-15a == 2004-08-22 == 2004-09-12 == 2004-09-25 == 2004-09-30 == 2004-11-01 == 2004-11-02 == 2004-11-10 == 2005-01-14 == 2005-01-15 == 2005-01-16a == 2005-02-06 == 2005-02-18 == 2005-05-07 == 2006-03-09e == 2006-06-04
CVE-2009-1960	High	June 8, 2009 6/8/09	== rc2009-02-06 == 2009-02-14 == rc2009-01-30

Showing vulnerabilities for 3 products matching "dokuwiki". Each product has independent pagination.

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.