How severe is CVE-2008-6651?

CVE-2008-6651 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2008-6651 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (88th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2008-6651?

CVE-2008-6651 affects Oxyproject Oxybox. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2008-6651?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2008-6651 published?

CVE-2008-6651 was published on 2009-04-07 and last updated on 2026-06-16.

CVE-2008-6651

CVE-2008-6651 is a critical-severity vulnerability in Oxyproject Oxybox with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-94.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 4% (88th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-94
Affected product: Oxyproject Oxybox
Published: 2009-04-07
Last modified: 2026-06-16

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.

Frequently asked questions

What is CVE-2008-6651?: 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.
How severe is CVE-2008-6651?: CVE-2008-6651 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2008-6651 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (88th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2008-6651?: CVE-2008-6651 affects Oxyproject Oxybox. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2008-6651?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2008-6651 published?: CVE-2008-6651 was published on 2009-04-07 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:oxyproject:oxybox:0.85:*:*:*:*:*:*:*

Other CWE-94 (Code Injection) vulnerabilities

CVE-2026-57624 — Critical (CVSS 10.0): Unauthenticated Remote Code Execution (RCE) in Blocksy Companion Pro <= 2.1.46 versions.
CVE-2026-10134 — Critical (CVSS 10.0): IBM Langflow OSS 1.0.0 through 1.9.3 allows an attacker to read every secret available to the Langflow process, read…
CVE-2026-53576 — Critical (CVSS 10.0): Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter…
CVE-2026-10561 — Critical (CVSS 10.0): IBM Langflow OSS 1.0.0 through 1.9.3 has an vulnerability due to an improper isolation of Python execution combined…
CVE-2026-25470 — Critical (CVSS 10.0): Improper Control of Generation of Code ('Code Injection') vulnerability in ACPT ACPT (Pro) - Custom Post Types Plugin…
CVE-2026-48836 — Critical (CVSS 10.0): Unauthenticated Remote Code Execution (RCE) in Easy Invoice <= 2.1.19 versions.

Browse all CWE-94 (Code Injection) vulnerabilities →