Menu

Star on GitHub · 3.2k

CVE-2006-1658

7.5 · HIGH

Direct static code injection vulnerability in ticker.db.php in Chucky A.

Published Apr 7, 2006chucky_a._iveyEPSS 1.55%

Overview

CVE-2006-1658 is a high-severity vulnerability affecting chucky_a._ivey n.t.. It was published on April 7, 2006 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Direct static code injection vulnerability in ticker.db.php in Chucky A. Ivey N.T. 1.1.0 allows remote administrators to insert arbitrary PHP code into the config file, which is included other N.T. scripts.

Remediation

Check the references section for vendor advisories and patches from chucky_a._ivey. Update n.t. to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2006-1658?

CVE-2006-1658 is a high-severity vulnerability affecting chucky_a._ivey n.t.. It was published on April 7, 2006 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2006-1658?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2006-1658?

Check the references section for vendor advisories and patches from chucky_a._ivey. Update n.t. to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2006-1658?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2006-1658 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2006

View all