CVE-2008-4769 in the critical feed json
Directory traversal vulnerability in the get_category_template function in wp-includes/theme.php in WordPress 2.3.3 and earlier, and 2.5, a…
published 2008-10-28 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-4749
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.0%
- EPSS 9.0% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in the get_category_template function in wp-includes/theme.php in WordPress 2.3.3 and earlier, and 2.5, allows remote attackers to include and possibly execute arbitrary PHP files via the cat parameter in index.php. NOTE: some of these details are obtained from third party information.
Patch / fix
- wordpress Debian 14, Debian 13, Debian 12 2.5.1-1
debian advisories DEBIAN-CVE-2008-4769
Timeline
- First public exploit (EDB-31670)
- Published
Exploit prediction
8.97% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-31670 WordPress Core 2.3.3 - 'cat' Directory Traversal webapps, 2008-04-18
- securityfocus.com http://www.securityfocus.com/bid/28845 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
-
securityfocus.com
/bid/28845
vdb-entry, exploit
-
debian.org
/security/2009/dsa-1871
vendor-advisory
-
secunia.com
/advisories/29949
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/41920
vdb-entry
- trac.wordpress.org /changeset/7586
- juniper.fi /security/auto/vulnerabilities/vuln28845.html
Sources
- CVE List CVE-2008-4769
- NVD CVE-2008-4769
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.