Menu

Star on GitHub · 3.2k

CVE-2008-6651

10.0 · HIGH

Static code injection vulnerability in edithistory.php in OxYProject OxYBox 0.85 allows remote attackers to inject arbitrary PHP code into oxyhistory.php via the oxymsg parameter.

Published Apr 7, 2009oxyprojectCWE-94EPSS 3.50%

Overview

CVE-2008-6651 is a high-severity vulnerability affecting oxyproject oxybox. It was published on April 7, 2009 and has a CVSS 2.0 base score of 10.0 (HIGH).

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

Technical description

Static code injection vulnerability in edithistory.php in OxYProject OxYBox 0.85 allows remote attackers to inject arbitrary PHP code into oxyhistory.php via the oxymsg parameter.

Remediation

Check the references section for vendor advisories and patches from oxyproject. Update oxybox 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-2008-6651?

CVE-2008-6651 is a high-severity vulnerability affecting oxyproject oxybox. It was published on April 7, 2009 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2008-6651?

This vulnerability has a CVSS 2.0 base score of 10.0, 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-2008-6651?

Check the references section for vendor advisories and patches from oxyproject. Update oxybox 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-2008-6651?

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

View all