Menu

Star on GitHub · 3.2k

CVE-2006-3911

7.5 · HIGH

PHP remote file inclusion vulnerability in OSI Codes PHP Live!

Published Jul 28, 2006php_liveEPSS 16.32%

Overview

CVE-2006-3911 is a high-severity vulnerability affecting php_live php_live. It was published on July 28, 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

PHP remote file inclusion vulnerability in OSI Codes PHP Live! 3.2.1 and earlier allows remote attackers to execute arbitrary PHP code via a URL in the css_path parameter in (1) help.php and (2) setup/header.php.

Remediation

Check the references section for vendor advisories and patches from php_live. Update php_live 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
php_livephp_live0Affected

Frequently asked questions

What is CVE-2006-3911?

CVE-2006-3911 is a high-severity vulnerability affecting php_live php_live. It was published on July 28, 2006 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2006-3911?

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

Check the references section for vendor advisories and patches from php_live. Update php_live 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-3911?

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