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.

346,508

Total vulnerabilities in the database

Vulnerabilities for products matching "php--nuke"

Found 3 matching products. Filters apply to all results.

You can search for specific versions with /product/php--nuke/1.2.3

francisco_burzi / php-nuke

684 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2004-0737	High	July 27, 2004 7/27/04	== 8.0_final
CVE-2004-0738	High	July 27, 2004 7/27/04	== 8.0_final
CVE-2004-2044	High	June 1, 2004 6/1/04	== 5.3.1 == 5.1 == 6.5_beta1 == 6.5 == 7.0 == 5.0 == 7.2 == 5.5 == 7.0_final == 5.4 == 6.5_rc2 == 5.2a == 7.3 == 6.5_rc3 == 5.0.1 == 5.2 == 5.6 == 6.0 == 6.5_final == 6.7 == 6.6 == 6.9 == 7.1 == 6.5_rc1
CVE-2004-1998	Medium	May 5, 2004 5/5/04	== 6.5 == 7.0 == 7.2 == 6.8 == 6.0 == 6.7 == 6.6 == 6.9 == 7.1
CVE-2004-1999	Low	May 5, 2004 5/5/04	== 6.5 == 7.0 == 7.2 == 6.8 == 6.0 == 6.7 == 6.6 == 6.9 == 7.1
CVE-2004-1984	Medium	May 2, 2004 5/2/04	== 7.0 == 7.2 == 7.0_final == 6.9 == 7.1
CVE-2004-1985	Low	April 30, 2004 4/30/04	== 7.0 == 7.2 == 7.0_final == 6.9 == 7.1
CVE-2004-1987	High	April 30, 2004 4/30/04	== 7.0 == 7.2 == 7.0_final == 6.9 == 7.1
CVE-2004-1988	High	April 30, 2004 4/30/04	== 7.0 == 7.2 == 7.0_final == 6.9 == 7.1
CVE-2004-1989	High	April 30, 2004 4/30/04	== 7.0 == 7.2 == 7.0_final == 6.9 == 7.1
CVE-2004-1972	High	April 26, 2004 4/26/04	== 7.2
CVE-2004-1929	High	April 13, 2004 4/13/04	== 6.5_beta1 == 6.5 == 7.0 == 7.2 == 5.5 == 7.0_final == 6.5_rc2 == 6.5_rc3 == 6.0 == 6.5_final == 6.7 == 6.6 == 6.9 == 7.1 == 6.5_rc1
CVE-2004-1930	Low	April 12, 2004 4/12/04	== 6.5_beta1 == 6.5 == 7.0 == 7.2 == 7.0_final == 6.5_rc2 == 6.5_rc3 == 6.0 == 6.5_final == 6.7 == 6.6 == 6.9 == 7.1 == 6.5_rc1
CVE-2004-1932	High	April 12, 2004 4/12/04	== 6.5_beta1 == 6.5 == 7.0 == 7.2 == 7.0_final == 6.5_rc2 == 6.5_rc3 == 6.0 == 6.5_final == 6.7 == 6.6 == 6.9 == 7.1 == 6.5_rc1
CVE-2004-1986	Medium	April 4, 2004 4/4/04	== 7.0 == 7.2 == 7.0_final == 6.9 == 7.1
CVE-2004-1839	Medium	March 22, 2004 3/22/04	== 6.5_beta1 == 6.5 == 7.0 == 7.0_final == 6.5_rc2 == 6.5_rc3 == 6.5_final == 6.7 == 6.6 == 6.9 == 6.5_rc1
CVE-2004-1840	Low	March 22, 2004 3/22/04	== 6.5_beta1 == 6.5 == 7.0 == 7.0_final == 6.5_rc2 == 6.5_rc3 == 6.5_final == 6.7 == 6.6 == 6.9 == 6.5_rc1
CVE-2004-1830	Medium	March 18, 2004 3/18/04	== 6.0
CVE-2004-1817	Low	March 15, 2004 3/15/04	== 7.1
CVE-2003-1210	High	December 31, 2003 12/31/03	== 6.5_beta1 == 6.5_rc2 == 6.5_rc3 <= 6.5 == 6.5_final == 6.5_rc1
CVE-2003-1400	Low	December 31, 2003 12/31/03	== 5.3.1 == 5.1 == 5.0 == 5.5 == 5.4 == 5.2a == 5.0.1 == 5.2 == 5.6 == 6.0
CVE-2003-1435	High	December 31, 2003 12/31/03	== 5.6 == 6.0
CVE-2003-1468	Low	December 31, 2003 12/31/03	== 6.5_beta1 == 6.5 == 6.5_rc2 == 6.5_rc3 == 6.0 == 6.5_final == 6.5_rc1
CVE-2003-1526	Medium	December 31, 2003 12/31/03	== 7.0
CVE-2003-1547	Low	December 31, 2003 12/31/03	== 6.5_beta1 == 6.5 == 6.5_rc2 == 6.5_rc3 == 6.5_rc1
CVE-2003-0279	Low	June 16, 2003 6/16/03	== 5.0 == 6.0
CVE-2003-0318	Low	June 9, 2003 6/9/03	<= 6.0
CVE-2002-1803	Low	December 31, 2002 12/31/02	== 6.0
CVE-2002-2032	Medium	December 31, 2002 12/31/02	== 4.0 == 5.3.1 == 5.1 == 4.3 == 1.0 == 4.4 == 2.5 == 3.0 == 5.0 == 5.4 == 5.2a == 5.0.1 == 5.2 == 4.4.1a
CVE-2002-1242	High	November 12, 2002 11/12/02	== 5.6
CVE-2002-0483	Medium	August 12, 2002 8/12/02	== 5.3.1 == 5.1 == 5.0 == 5.4 == 5.2a == 5.0.1 == 5.2
CVE-2002-0206	High	May 16, 2002 5/16/02	== 4.0 == 5.3.1 == 5.1 == 4.3 == 1.0 == 4.4 == 2.5 == 3.0 == 5.0 == 5.2a == 5.0.1 == 5.2 == 4.4.1a
CVE-2001-1522	Low	December 31, 2001 12/31/01	== 8.0_final
CVE-2001-1524	Low	December 31, 2001 12/31/01	== 4.0 == 5.3.1 == 5.1 == 4.3 == 4.4 == 3.0 == 5.0 == 5.2a == 5.0.1 == 5.2 == 4.4.1a
CVE-2001-0854	Medium	December 6, 2001 12/6/01	== 5.2
CVE-2001-0911	High	November 21, 2001 11/21/01	== 5.3.1 == 5.1 == 5.2
CVE-2001-1032	High	September 24, 2001 9/24/01	<= 5.2
CVE-2001-1025	High	August 31, 2001 8/31/01	== 5.0 == 5.0.1
CVE-2001-0383	Medium	June 18, 2001 6/18/01	<= 4.4
CVE-2001-0001	High	June 2, 2001 6/2/01	== 4.4
CVE-2001-0292	High	May 3, 2001 5/3/01	== 4.4.1a
CVE-2001-0320	High	May 3, 2001 5/3/01	== 4.4 == 4.0.4
CVE-2001-0321	Medium	May 3, 2001 5/3/01	== 8.0_final
CVE-2000-0745	High	October 20, 2000 10/20/00	== 1.0 == 2.5

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