CVE-2008-6651: Static code injection vulnerability in edithistory.php in OxYProject OxYBox 0.85 allows remote attackers to in
CVE-2008-6651 is a high-severity flaw (CVSS 10.0) affecting oxybox. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Critical severity
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 10.0 (High) |
| EPSS exploit chance | 3.5% (top 11%) |
| CISA exploited list | No |
| Weakness | CWE-94 |
| Published | 2009-04-07 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Public exploits and detection
Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2008-6651?
oxybox: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2008-6651 being exploited?
CVE-2008-6651 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2008-6651 affect?
CVE-2008-6651 affects oxybox. Severity is high (CVSS 10.0). 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 urgent is CVE-2008-6651?
Priority 62/100. Critical severity; Public exploit reference