First published: Wed Dec 21 2005(Updated: )
WordPress before 1.5.2 allows remote attackers to obtain sensitive information via a direct request to (1) wp-includes/vars.php, (2) wp-content/plugins/hello.php, (3) wp-admin/upgrade-functions.php, (4) wp-admin/edit-form.php, (5) wp-settings.php, and (6) wp-admin/edit-form-comment.php, which leaks the path in an error message related to undefined functions or failed includes. NOTE: the wp-admin/menu-header.php vector is already covered by CVE-2005-2110. NOTE: the vars.php, edit-form.php, wp-settings.php, and edit-form-comment.php vectors were also reported to affect WordPress 2.0.1.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
WordPress | =1.0 | |
WordPress | =1.0.1 | |
WordPress | =1.0.2 | |
WordPress | =1.2 | |
WordPress | =1.5 | |
WordPress | =1.5.1 | |
WordPress | =1.5.1.2 | |
WordPress | =1.5.1.3 | |
WordPress | =2.0.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2005-4463 is classified as a moderate severity vulnerability due to the potential disclosure of sensitive information.
To fix CVE-2005-4463, it is recommended to upgrade WordPress to version 1.5.2 or later.
CVE-2005-4463 affects WordPress versions prior to 1.5.2.
CVE-2005-4463 allows remote attackers to obtain sensitive information from specific PHP files through direct requests.
General mitigation for CVE-2005-4463 involves restricting direct access to vulnerable files and applying security updates promptly.