How severe is CVE-2008-6767?

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

Is CVE-2008-6767 being actively exploited?

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

What products are affected by CVE-2008-6767?

CVE-2008-6767 affects Wordpress. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2008-6767?

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-6767 published?

CVE-2008-6767 was published on 2009-04-28 and last updated on 2026-06-16.

CVE-2008-6767

CVE-2008-6767 is a critical-severity vulnerability in Wordpress 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.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 5% (91st percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Wordpress
Published: 2009-04-28
Last modified: 2026-06-16

Description

wp-admin/upgrade.php in WordPress, probably 2.6.x, allows remote attackers to upgrade the application, and possibly cause a denial of service (application outage), via a direct request.

Frequently asked questions

What is CVE-2008-6767?: wp-admin/upgrade.php in WordPress, probably 2.6.x, allows remote attackers to upgrade the application, and possibly cause a denial of service (application outage), via a direct request.
How severe is CVE-2008-6767?: CVE-2008-6767 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2008-6767 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2008-6767?: CVE-2008-6767 affects Wordpress. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2008-6767?: 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-6767 published?: CVE-2008-6767 was published on 2009-04-28 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:wordpress:wordpress:2.6:*:*:*:*:*:*:*

More vulnerabilities in Wordpress

CVE-2012-2400 — Critical (CVSS 10.0): Unspecified vulnerability in wp-includes/js/swfobject.js in WordPress before 3.3.2 has unknown impact and attack…
CVE-2012-2399 — Critical (CVSS 10.0): Cross-site scripting (XSS) vulnerability in swfupload.swf in SWFupload 2.2.0.1 and earlier, as used in WordPress before…
CVE-2011-3125 — Critical (CVSS 10.0): Unspecified vulnerability in WordPress 3.1 before 3.1.3 and 3.2 before Beta 2 has unknown impact and attack vectors…
CVE-2011-3122 — Critical (CVSS 10.0): Unspecified vulnerability in WordPress 3.1 before 3.1.3 and 3.2 before Beta 2 has unknown impact and attack vectors…
CVE-2009-2853 — Critical (CVSS 10.0): Wordpress before 2.8.3 allows remote attackers to gain privileges via a direct request to (1) admin-footer.php, (2)…
CVE-2008-4796 — Critical (CVSS 10.0): The _httpsrequest function (Snoopy/Snoopy.class.php) in Snoopy 1.2.3 and earlier, as used in (1) ampache, (2)…

All CVEs affecting Wordpress →