Menu

Star on GitHub · 3.2k

CVE-2007-2006

7.5 · HIGH

Multiple SQL injection vulnerabilities in login.php in pL-PHP beta 0.9 allow remote attackers to execute arbitrary SQL commands via the (1) login or (2) pass parameter.

Published Apr 12, 2007pl-phpEPSS 1.03%

Overview

CVE-2007-2006 is a high-severity vulnerability affecting pl-php pl-php. It was published on April 12, 2007 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

Multiple SQL injection vulnerabilities in login.php in pL-PHP beta 0.9 allow remote attackers to execute arbitrary SQL commands via the (1) login or (2) pass parameter.

Remediation

Check the references section for vendor advisories and patches from pl-php. Update pl-php 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
pl-phppl-php0Affected

Frequently asked questions

What is CVE-2007-2006?

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

How severe is CVE-2007-2006?

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-2007-2006?

Check the references section for vendor advisories and patches from pl-php. Update pl-php 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-2007-2006?

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

View all