Menu

Star on GitHub · 3.2k

CVE-2006-1576

7.5 · HIGH

Direct static code injection vulnerability in QLnews 1.2 allows remote authenticated administrators to execute arbitrary PHP code by modifying config.php.

Published Apr 2, 2006vscripts.plEPSS 1.75%

Overview

CVE-2006-1576 is a high-severity vulnerability affecting vscripts.pl qlnews. It was published on April 2, 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 QLnews 1.2 allows remote authenticated administrators to execute arbitrary PHP code by modifying config.php.

Remediation

Check the references section for vendor advisories and patches from vscripts.pl. Update qlnews 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-1576?

CVE-2006-1576 is a high-severity vulnerability affecting vscripts.pl qlnews. It was published on April 2, 2006 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2006-1576?

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-1576?

Check the references section for vendor advisories and patches from vscripts.pl. Update qlnews 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-1576?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2006-1576 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