Reported vulnerability

WordPress Core <= 2.3.3 - Directory Traversal

Q: Which versions of WordPress are affected?

Wordfence lists these affected versions: Start version unspecified, through 2.3.3; From 2.5, through 2.5. Use the version checker above to compare your installed release with this report.

Q: Is a fix available for WordPress?

Wordfence reports a fix for this issue in WordPress. It lists these fixed versions: 2.5.1. Back up your website and test the recommended update before applying it to your live site.

Q: Where can I find my installed WordPress version?

In WordPress, open Dashboard > Updates to find your installed WordPress version.

Published 25 Apr 2008

Updated 22 Jan 2024

CVE-2008-4769

Compare your installed software with the affected versions below. Follow the source’s remediation guidance and test an available update after taking a backup. A database entry describes a reported issue; it does not establish whether a particular website has been compromised.

Does this affect my version?

Check your installed version against this advisory. This compares the report’s version ranges and does not scan your website.

Wordfence advisory

high · CVSS 7.5

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.

Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

WordPress

Software: WordPress Core · wordpress
Affected versions: Start version unspecified, through 2.3.3; From 2.5, through 2.5
Fix availability: Fix available
Fixed versions: 2.5.1

Recommended action

Update to version 2.5.1, or a newer patched version

Further references (1)

wordfence.com/threat-intel/vulnerabilities/id/38b27ee7-0e92-47ad-89f8-1a3c8d5c9442?source=api-prod

Data sources and licences

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Read licence terms

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

Read licence terms

Source: Wordfence

Need help fixing this issue?

Get help checking your site, applying an available update and resolving any problems after updating.

Get help with this issue

Questions about this vulnerability

Which versions of WordPress are affected?

Wordfence lists these affected versions: Start version unspecified, through 2.3.3; From 2.5, through 2.5. Use the version checker above to compare your installed release with this report.

Is a fix available for WordPress?

Wordfence reports a fix for this issue in WordPress. It lists these fixed versions: 2.5.1. Back up your website and test the recommended update before applying it to your live site.

Where can I find my installed WordPress version?

In WordPress, open Dashboard > Updates to find your installed WordPress version.

Does an affected version mean my website has been hacked?

An affected version means the installed release matches a vulnerability described in this report. It does not show whether anyone has exploited it on your website. The checker compares version numbers with stored reports; it does not inspect your website.

These reports cover at least one of the same plugins, themes or WordPress core. Check each report’s affected versions separately.

Back to vulnerability database