Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2008-6651: Static code injection vulnerability in edithistory.php in OxYProject OxYBox 0.85 allows remote attackers to in

62
This week
HIGH 10.0DOWNGRADE

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 score10.0 (High)
EPSS exploit chance3.5% (top 11%)
CISA exploited listNo
WeaknessCWE-94
Published2009-04-07
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: oxyproject

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

oxyproject oxybox DOWNGRADE
Affected: 0.85
Fixed in: no fixed release known
Safe to downgrade to: a release before 0.85
1. Check installed version
apt-cache policy oxybox || rpm -q oxybox || oxybox --version
2. No fixed release: DOWNGRADE to a release before 0.85 (Debian / Ubuntu)
apt-cache madison oxybox sudo apt install oxybox=<VERSION_BEFORE_0.85> sudo apt-mark hold oxybox
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list oxybox sudo dnf downgrade oxybox-<VERSION_BEFORE_0.85> sudo dnf versionlock add oxybox
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
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

Software pages

PHP vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.